-
Tested with success here
-
@stormi All good with updating my playlab.
-
Seems to be working fine for me as well.
-
We found and fixed a regression in the update candidate for
smregarding shared thick-provisioned drivers based on LVM (lvmoiscsiand others).Please update again (mirrors will receive the within 15 minutes) using the command given above. This will give you
smandsm-rawhbain version-release2.30.7-1.3.xcpng8.2. -
@stormi Can not help with the
smandsm-rawhbaregression, but did the update anyway. Worked well and kicking some VMs around works as expected. Let's see how my playlab does during the weekend. -
@stormi
is there some information about that regression?
maybe i can help to test.
have a lab pool here with 3 hosts on a iscsi SR. -
Hello,
This thread appears to be for testing update candidate releases. Where can I find the release notes for production ready updates?
Thx
-
Any functional change will be explained in our blog. Other updates are mostly security (see the security tag on the blog: https://xcp-ng.org/blog/tag/security)
-
New security update (xen, Intel and AMD CPUs)
Xen is being updated to mitigate hardware vulnerabilities in Intel and AMD CPUs.
- Upstream (Xen project) advisory: XSA-407
- Citrix Hypervisor Security Bulletin: https://support.citrix.com/article/CTX461397/citrix-hypervisor-security-bulletin-for-cve202223816-and-cve202223825
Impact of the vulnerabilities - RETbleed is a speculative execution attack on x86-64 processors, including some recent Intel and AMD chips. You can read the original paper from Computer Security Group at this address: https://comsec.ethz.ch/research/microarch/retbleed/
Test on XCP-ng 8.2
From an up to date host:
yum clean metadata --enablerepo=xcp-ng-testing yum update xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools --enablerepo=xcp-ng-testing rebootVersions:
- xen-*: 4.13.4-9.24.1.xcpng8.2
What to test
Normal use and anything else you want to test. The closer to your actual use of XCP-ng, the better.
Test window before official release of the updates
~2 days.
-
Tested in my lab, so far so good.
More testers means faster release
-
@gduperrey This update breaks the XOSTOR setup in my test lab. Would you like any information from me for troubleshooting? If not, what's the easiest way to revert the test updates?
-
Hmm no reason for that, did you have other updates coming with it? (ie replacing some other unrelated packages).
-
Adding @ronan-a in the loop.
When you said "break", can you be more specific @JeffBerntsen ?
-
@olivierlambert said in Updates announcements and testing:
Adding @ronan-a in the loop.
When you said "break", can you be more specific @JeffBerntsen ?
@olivierlambert said in Updates announcements and testing:
Hmm no reason for that, did you have other updates coming with it? (ie replacing some other unrelated packages).
I have 3 servers in my lab's test pool, vh97, vh98, and vh99. Server vh97 was the pool master. I placed it into maintenance mode and shifted the pool master to vh98 in the process, installed the updates, and rebooted.
When vh97 came back up, it could no longer attach to the XOSTOR SR. Attempting to replug the PBD gives me errors indicating that vh97 can no longer see the SR. It appears that there are some related errors in the SMlog file (I've captured a copy for future examination).
The updates installed were only the ones from this most recent set. All of the other test updates from this thread from the last two weeks were already installed and running without problems on all 3 servers in the pool.
-
If you test XOSTOR, don't test other updates, because this might break the rest.
Also, never switch the master after updates, the master HAS to reboot first, whatever happens.
-
@olivierlambert said in Updates announcements and testing:
If you test XOSTOR, don't test other updates, because this might break the rest.
Also, never switch the master after updates, the master HAS to reboot first, whatever happens.
I know that XOSTOR might break during an update test. I thought whether it did or didn't might be something you would be interested in as part of testing and that's part of why I test with it in place and running.
-
@JeffBerntsen What's your sm version? I suppose, you updated your hosts and you don't have the right one.
Please send me the output of:
rpm -qa | grep sm-. -
@ronan-a said in Updates announcements and testing:
@JeffBerntsen What's your sm version? I suppose, you updated your hosts and you don't have the right one.
Please send me the output of:
rpm -qa | grep sm-.Definitely possible although it appears they were updated as part of installing the previous updates in this thread from the past couple of weeks.
What I have is:
sm-cli-0.23.0-6.xcpng8.2.x86_64 sm-rawhba-2.30.7-1.3.xcpng8.2.x86_64 sm-2.30.7-1.3.xcpng8.2.x86_64 -
@JeffBerntsen I think I will release a new
linstorRPM to override thesmtesting package. The current is:sm-2.30.7-1.2.0.linstor.1.xcpng8.2.x86_64.rpm. For the moment, you can downgrade if you want. -
@ronan-a said in Updates announcements and testing:
@JeffBerntsen I think I will release a new
linstorRPM to override thesmtesting package. The current is:sm-2.30.7-1.2.0.linstor.1.xcpng8.2.x86_64.rpm. For the moment, you can downgrade if you want.That seems to have taken care of it. Left all upgraded versions from this thread in place except for sm and sm-rawhba which have been downgraded to the linstor versions from the regular repo. All seems to be working well now.
