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

Add troubleshooting rex timeout due to yggdrasil version #3516

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

asteflova
Copy link
Member

@asteflova asteflova commented Dec 10, 2024

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

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.13/Katello 4.15
  • Foreman 3.12/Katello 4.14 (Satellite 6.16)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • Foreman 3.8/Katello 4.10
  • Foreman 3.7/Katello 4.9 (Satellite 6.14)
  • We do not accept PRs for Foreman older than 3.7.

@asteflova
Copy link
Member Author

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.

Copy link
Contributor

@maximiliankolb maximiliankolb left a 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.

@maximiliankolb maximiliankolb added style review done No issues from docs style/grammar perspective Needs tech review Requires a review from the technical perspective labels Dec 11, 2024
@asteflova
Copy link
Member Author

Tech review was covered in #3492 where I originally worked on this, so I'll add the label here as well.

@asteflova asteflova added tech review done No issues from the technical perspective and removed Needs tech review Requires a review from the technical perspective labels Dec 11, 2024
@asteflova
Copy link
Member Author

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.

Based on #3492 (comment), it looks like it doesn't apply.

@maximiliankolb
Copy link
Contributor

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.

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!

@asteflova
Copy link
Member Author

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.

@asteflova
Copy link
Member Author

I'm adding waiting for code while we wait for packaging PRs.

@asteflova asteflova added the Waiting for code Requires merge of related code in another repository before it can be merged label Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
style review done No issues from docs style/grammar perspective tech review done No issues from the technical perspective Waiting for code Requires merge of related code in another repository before it can be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants