-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update troubleshooting guide #3552
Conversation
Signed-off-by: David Espejo <[email protected]>
Merge upstream branch
Signed-off-by: David Espejo <[email protected]>
Signed-off-by: David Espejo <[email protected]>
Signed-off-by: David Espejo <[email protected]>
Signed-off-by: David Espejo <[email protected]>
Signed-off-by: David Espejo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's convert all the headers that use ~
to use ^
(see here)
rsts/community/troubleshoot.rst
Outdated
|
||
.. tags:: Troubleshoot, Basic | ||
|
||
.. admonition:: Why did we craft this guide? | ||
The content in this section will help Flyte users isolate the most possible causes for some of the common issues that could arise while getting started with the project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The content in this section will help Flyte users isolate the most possible causes for some of the common issues that could arise while getting started with the project. | |
The content in this section will help Flyte users isolate the most probable causes for some of the common issues that could arise while getting started with the project. |
|
||
How Do I Debug? | ||
""""""""""""""" | ||
$ kubectl describe pod <PodName> -n <namespace> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be worth calling out that <PodName>
will typically correspond to the node execution string that you can find in the UI
|
||
.. prompt:: bash $ | ||
|
||
docker ps | ||
$ kubectl logs pods -n <namespace> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also might be worth calling out that <namespace>
will typically be the Flyte <project>-<domain>
, e.g. flytesnacks-development
|
||
.. code-block:: | ||
Depending on the contents of the logs or the `Events`, you can try different things: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we group all the errors here into another subheading? So similar to "Issues running workloads", maybe we can add a header in this section like "Debugging common execution errors"
Signed-off-by: David Espejo <[email protected]>
Signed-off-by: David Espejo <[email protected]>
Signed-off-by: David Espejo <[email protected]>
Tracking issue
Implements the idea of #3340
Describe your changes
Check all the applicable boxes
Screenshots
Note to reviewers