@olivierlambert updating the README will be quick enough... but if the sig is indeed mandatory we need to setup something for this first... and autosigning from a CI rather requires doing that on a trusted runner rather than on gitlab-provided ones, so that requires some provisioning and IT work first.
Team - OS Platform & Release
Posts
-
RE: New Rust Xen guest tools
-
RE: XCP-ng 8.3 updates announcements and testing
New update candidate for you to test!
A new non-urgent update is ready for user testing before a future collective release. Below are the details.
Maintenance updates
broadcom-bnxt-en
: Update driver to version 1.10.3_232.0.155.5
Test on XCP-ng 8.3
yum clean metadata --enablerepo=xcp-ng-testing yum update --enablerepo=xcp-ng-testing reboot
A reboot is preferable to load the new version of the driver.
The usual update rules apply: pool coordinator first, etc.
Versions:
broadcom-bnxt-en
: 1.10.3_232.0.155.5-1.xcpng8.3
What to test
Normal use and anything else you want to test.
Test window before official release of the updates
None defined, but early feedback is always better than late feedback, which is in turn better than no feedback
-
RE: XCP-ng 8.3 updates announcements and testing
New update candidate for you to test!
A new non-urgent update is ready for user testing before a future collective release. Below are the details.
A bug was found in the Emergency Network Reset due to desynchronisation between
xsconsole
and XAPI. This issue prevented the Emergency Network Reset from working at all. This update includes the fixes from the upstreamxsconsole
project to fix it.
Maintenance updates
xsconsole
- Backport sync of network reset trigger file path with XAPI to fix emergency network reset
- Backport fix for pool.conf IPv6 to avoid IPv6 truncation
Test on XCP-ng 8.3
yum clean metadata --enablerepo=xcp-ng-testing yum update --enablerepo=xcp-ng-testing reboot
Reboot is not strictly necessary, but the
xsconsole
instance running on the first virtual terminal of your host won't be restarted otherwise. If you do not reboot, make sure to startxsconsole
from another terminal after the update.The usual update rules apply: pool coordinator first, etc.
Versions:
xsconsole
: 11.0.8-1.2.xcpng8.3
What to test
Normal xsconsole usage, is still useful feedback. However, if possible, the most helpful test would be performing an Emergency Network Reset through
xsconsole
, making actual configuration changes and verifying that they are correctly applied after reboot.Test window before official release of the updates
None defined, but early feedback is always better than late feedback, which is in turn better than no feedback