XCP-ng 8.3 updates announcements and testing
-
@acebmxer said:
(...)
yum history undo <ID> --enablerepo=xcp-ng-testing
(...)Your're lucky ! this is a risky operation we don't recommend to downgrade because some packages like xapi are not handling this properly, prefer other workarounds if there are any (like disabling nbd until @storage team suggest a better option)
Let me thank you again @flakpyro for this regression report it is very valuable to us,
-
@lmolina Updates ran fine, but I'm having CR backup problems too... Mostly ran fine, but I now have 3 stuck with
VBD.unplug_force. I can't get them to clear. I'll have to try harder before I revert updates. -
@rzr I was worried about this because of XAPI. Luckily i have a host thats not currently running any VMs so i tried it there first hoping it was a small enough change that i could get away with it. Good to know i could have just disabled NBD for now though!
-
@acebmxer said:
(...)
yum history undo <ID> --enablerepo=xcp-ng-testing
(...)Your're lucky ! this is a risky operation we don't recommend to downgrade because some packages like xapi are not handling this properly, prefer other workarounds if there are any (like disabling nbd until @storage team suggest a better option)
Let me thank you again @flakpyro for this regression report it is very valuable to us,
I didn't run the commands I stated. As I was asking first.. I did the command @flakpryo
Of course this is was before i saw your post. As this is the home lab i am fine with if it blows up. but for others this is good to know.
-
We have just released security updates for
ca-certificates.Full details are available on the blog:
https://xcp-ng.org/blog/2026/10/22/october-2026-security-updates-3-for-xcp-ng-8-3-lts/ -
Ok, so what's the scoop here? Safe to roll this out or wait a few days? I just saw the notice in my XO that there are updates and I don't want to wreck my system right now after fixing a few other "issues".
[edit] I see this is just the certificate update so pushing it out and listening to servers reboot.
-
I reinstalled the updates, and confirm backups work with NBD disablled in backup job. - I missed the part about NBD in the notes..
However the task stay at 0% while i can see traffic on my trunas..
-
jr-m4 said:
Updated two dev-pools successfully!
new-xcp-dev: 2x Dell Inc. PowerEdge R650xs
old-xcp-dev: 3x Dell Inc. PowerEdge R350 (HA)I even mistankenly did a wrong updating order on old-xcp-dev. And neglected to disable HA before updating, leading to two hosts being updated and promoting the next master. And by chance the last master was the non-updated one. Here I disabled HA, but couldn't promote another master (not unexpected)... Post update, and everything seems to be good anyways. And HA re-enabled successfully
Note:
No further testing other than the hosts booting and showing good life signs have been done, yet.I'm now also seeing issues with backups being stuck for multiple hours.
Update: Correction. I'm now having issues with almost everything on both pools.- migrations
- snapshots
- changing status e.g. rebooting or hard shut down of VMs
-
@lmolina @olivierlambert Sorry, but this update got ugly fast. CR backups got stuck. Migrations got stuck. VMs would not start any more. After reverting all the patches and rebooting all hosts I had several VMs that would not start again (including primary XO) because the VDIs stuck marked as activating. It took some time to fix them but at least there was no data loss. Some backups lost their snapshots and had to revert to full backups again.
-
Some message formats changed between the two releases, so VMs started before the update (with an 11.3 tapdisk and tapback) can’t understand some of the changed commands. Rebooting XCP-ng or doing an RPU should work. Since not every command is affected, restarting tapback is usually enough: systemctl restart tapback.service
We're going to work to avoid that. -
Rebooting hosts and/or VMs doesn't solve the problems.
As @andrew said. This one got ugly. But this is also why we test stuffUpdate:
Doing a "Rescan all disks" on the SR (lvmohba), seems to help out a little bit. But not everything.
Some VMs were able to be started again. But others are still showing problems and erroring out"The VDI is not available [opterr=['MAP_DUPLICATE_KEY', 'VDI', 'sm_config', 'OpaqueRef:7---------2c1b', 'activating']]",
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login