-
Notifications
You must be signed in to change notification settings - Fork 95
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
Add troubleshooting rex timeout due to yggdrasil version #3516
base: master
Are you sure you want to change the base?
Add troubleshooting rex timeout due to yggdrasil version #3516
Conversation
The PR preview for f133cc5 is available at theforeman-foreman-documentation-preview-pr-3516.surge.sh The following output files are affected by this PR: |
After/if this gets merged, a reference in the upgrade docs (probably nightly/3.14) would be appropriate. Users might run into the issue on hosts with weak dependencies disabled, a reference in the upgrade guide would hopefully help prevent that. |
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.
Style-wise this LGTM. I wonder if the same applies to all Client OS. If so, I'll check internally if we want to expand the docs for SLES and Debian/Ubuntu in a timely manner.
Tech review was covered in #3492 where I originally worked on this, so I'll add the label here as well. |
Based on #3492 (comment), it looks like it doesn't apply. |
for upstream :) Let me check downstream for orcharhino Clients. Nothing that blocks your PR! |
I'm waiting for a verification on which versions to cherry-pick to. Just to be sure, I'll switch this to draft while that gets resolved. |
I'm adding |
What changes are you introducing?
Users can now end up with different versions of yggdrasil on their host. This PR adds steps to troubleshoot potential issues and remedy them.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
This was originally included in #3492 but we should cherry-pick the troubleshooting part to earlier versions, hence a separate PR.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
More packages should get names as epic as yggdrasil.
Checklists
Please cherry-pick my commits into: