doc(common-problems.md): add troubleshooting section on yum update failures #414
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Explain why yum update fails with HTTPS 301 errors after fresh install Clarify the root cause and provide a step-by-step fix. Add a recommendation for post-install NTP setup to prevent SSL certificate issues. Signed-off-by: Thomas Moraine <thomas.moraine@vates.tech>
thomas-dkmt
changed the title
stormi
reviewed
Nov 18, 2025
|
|
||
| ### Symptoms | ||
|
|
||
| After installing XCP-ng 8.3, `yum update` or yum upgrade`` may fail with: |
Member
There was a problem hiding this comment.
No need to mention yum upgrade. Anyway I think he're we're missing the fact that most users will see this error in Xen Orchestra, first. Using yum update to update is a secondary update method, but maybe not the most used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR expands the Troubleshooting → Common problems page in the XCP-ng documentation.
We explain why
yum updatefails with HTTPS 301 errors after a fresh XCP 8.3 install, clarify the root cause and provide a step-by-step fix, in response to an issue reported in the XCP-ng forum.