@manilx We recently upgraded our Koji build system. This may have caused disruptions in this recent update release yesterday, where an XML file was generated multiple times. This has now been fixed and should not happen again. This may explain the issue encountered this time, particularly with the notification of updates via XO.
Note that normally yum metadata expires after a few hours and so it should normally return to normal on its own.
@manilx said in XCP-ng 8.3 updates announcements and testing:
yum clean all
I can't explain it. I can't say what's going on on your system, especially with so little information.
Personally, I run the following commands all the time:
yum clean metadata ; yum update
I very rarely need to use yum clean all, and I don't remember having to do an additional rm. And yet, I run the above commands a lot during testing campaigns.
@flakpyro Yes, it always takes a little time for the mirrors to synchronize.
I'm getting correct feedback from the main repository (https://updates.xcp-ng.org/) with the correct updates available.
Updates published: https://xcp-ng.org/blog/2025/07/15/july-2025-security-update-2-for-xcp-ng-8-3-lts/
Thank you for the tests!
Also note that there is a simpler approach if you don't need an "all-in-one" ISO image: driver disks.
You can build driver disks using https://github.com/xcp-ng/driver-disks and load them during the installation.
You can also ask us to provide driver disks for alternate drivers for which we haven't built them yet. We make them available on https://mirrors.xcp-ng.org/isos/drivers/8.x/...
That's also something we need to document in the official docs. It's mentioned in the release notes for 8.3 but not in other sections of the documentation.
And fixes for XCP-ng 8.2 are coming but they require more work to backport the patches.
I moved this discussion to its own topic, as we need the other one for update candidate testing.
A new XSA (Xen Security Advisory) was published on the 8th of July, related to hardware vulnerabilities in several AMD CPUS. Updated microcode mitigate it, and Xen is updated to adapt to the changes in the CPU features. We also publish other non-urgent updates which we had in the pipe for the next update release.
amd-microcode:
xen-*:
http-nbd-transfer:
xo-lite: update to 0.12.1
yum clean metadata --enablerepo=xcp-ng-testing
yum update --enablerepo=xcp-ng-testing
reboot
The usual update rules apply: pool coordinator first, etc.
amd-microcode: 20250626-1.1.xcpng8.3http-nbd-transfer: 1.7.0-1.xcpng8.3xen: 4.17.5-15.1.xcpng8.3xo-lite: 0.12.1-1.xcpng8.3Normal use and anything else you want to test.
~2 days.
We're not yet familiar with Netdata Cloud. Could you describe your requirements in more detail? What are you trying to accomplish?
The installation and use of third-party packages for XCP-ng is described in the following documentation: https://docs.xcp-ng.org/management/additional-packages/
We currently offer a version of Netdata in our repositories, but as a best-effort support option.
If you install a version from another source, this is not supported by us. You must therefore be careful to ensure that what you install does not overwrite or modify packages already present and used by XCP-ng. Furthermore, this will not persist during a server upgrade (a major version change, such as from 8.2 to 8.3, for example), and you will need to install it again, taking the same precautions.
