Skip to content

doc(common-problems.md): add troubleshooting section on yum update failures #414

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.

Sign up for GitHub

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

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

doc(common-problems.md): add troubleshooting section on yum update failures #414

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions docs/troubleshooting/common-problems.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -271,3 +271,37 @@ It should be empty, but if you have the bug, you got `check_update`.
Remove `/var/lib/xcp-ng-xapi-plugins/updater.py.lock` and that should fix it.

---

## Yum update fails after fresh install

### Symptoms

After installing XCP-ng 8.3, `yum update` or yum upgrade`` may fail with:
Copy link
Member

@stormi stormi Nov 18, 2025

Choose a reason for hiding this comment

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

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.


```
HTTPS Error 301 - Moved Permanently
failure: repodata/repomd.xml from xcp-ng-base: [Errno 256] No more mirrors to try.
```

:::note
The same URL might work fine from another machine, making the issue seem random.
:::

### Root cause

The problem is usually caused by an **incorrect system clock**. If the host’s date is way off (e.g., stuck in 2019), SSL certificates for XCP-ng mirrors appear invalid or "not yet valid," causing YUM to reject HTTPS connections.

This happens when the host hasn’t synced its time via NTP (e.g., missing or incorrect NTP settings from DHCP).

### Solution

1. Open XSConsole.
2. Set NTP sync (not using DHCP).
4. Apply changes and verify the system time updates correctly.
5. Run `yum update`.

Updates should now work without modifying repository URLs.

### Recommendation

Configure NTP properly right after installation, especially if DHCP does not provide NTP information. A correct system clock avoids SSL errors and repository access issues.