We pushed the updates to the xcp-ng-updates repository: https://xcp-ng.org/blog/2026/05/21/may-2026-updates-3-for-xcp-ng-8-3-lts/
Changed since the initial announcement, xen was updated with the proper vulnerability fix and an update to sm was added to fix an issue on LVM-based SRs with CBT enabled.
Thanks everyone for your feedback!
I didn't wait long enough for XO to catch up, the manual backup I did after rebooting the VM worked, I'll hit the other VM before I start some other work and see what I see. If I don't respond back toady, then it was a "dirty" VM because of some odd reboot condition. I've just never seen that before and odd that it happened 8 days after installing MS updates.
@Mathieu-L
linstor n l was included in my original post.
All nodes were updated to May 2026 Security and Maintenance Updates for XCP-ng 8.3 LTS, all nodes were restarted.
May 2026 Updates #2 for XCP-ng 8.3 LTS was released, and a couple days later I installed on all hosts. No host restarted.
When xen04 was restarted, that is when this issue happened.
I had used systemctl restart linstor-controller here (https://xcp-ng.org/forum/post/105309) to restart the controller.
