Skip to content
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

Merged
merged 10 commits into from
Apr 20, 2023
Merged

Update troubleshooting guide #3552

merged 10 commits into from
Apr 20, 2023

Conversation

davidmirror-ops
Copy link
Contributor

@davidmirror-ops davidmirror-ops commented Mar 29, 2023

Tracking issue

Implements the idea of #3340

Describe your changes

Check all the applicable boxes

  • I updated the documentation accordingly.
  • All new and existing tests passed.
  • All commits are signed-off.

Screenshots

Note to reviewers

@davidmirror-ops davidmirror-ops added this to the 1.6.0 milestone Apr 16, 2023
@davidmirror-ops davidmirror-ops linked an issue Apr 16, 2023 that may be closed by this pull request
2 tasks
@davidmirror-ops davidmirror-ops added the documentation Improvements or additions to documentation label Apr 16, 2023
@davidmirror-ops davidmirror-ops modified the milestones: 1.6.0, 1.5.0 Apr 17, 2023
Copy link
Contributor

@cosmicBboy cosmicBboy left a 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)


.. 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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>
Copy link
Contributor

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>
Copy link
Contributor

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:
Copy link
Contributor

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"

@davidmirror-ops davidmirror-ops merged commit 478137b into flyteorg:master Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Docs] Add User Guide section: Debugging Flyte
2 participants