New packages in xcp-ng-testing for the next XCP-ng 8.3 LTS maintenance update
This is a follow-up of the the previous post and addresses the issue reported by our testers.
First of all, a huge thanks to all testers who allowed us to catch this backup issue early:
@acebmxer, @jr-m4, @bufanda, @flakpyro, @Andrew.
We decided to revert the change that improves the performance of xapi-nbd since it caused the backup issue. This change will be reworked and refined, then presented to you again in a future update, without this issue. While investigating, we also found a bug in blktap: in rare cases, the process handling a VM disk (tapdisk) could crash during a backup and leave the disk impossible to detach. The new blktap version fixes it.
Versions
blktap: 3.55.5-12.2.xcpng8.3 -> blktap-3.55.5-12.3.xcpng8.3
xapi: 26.1.21-1.1.xcpng8.3 -> 26.1.21-1.2.xcpng8.3
Test on XCP-ng 8.3
yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates
yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates
reboot
If you reverted the previous candidates with yum history undo, update normally with the commands above. Note that downgrading is not recommended. If you disabled NBD in your backup jobs as a workaround, please enable it again after the update.
The usual update rules apply: pool coordinator first, etc.
What to test
If you have already carried out the initial updates and performed the tests mentioned in our previous post, please confirm that the XO backups are now back to a working state.
If you did not run the initial update and have not yet performed any tests, please be sure to review the "what to test" section of the the previous post.
Test window before official release of the updates
~7 days
