Nice catch @dthenot !
administrators
Private
Posts
-
RE: XCP-ng 8.3 updates announcements and testing
@Andrew Hello,
I have been able to find the problem and make a fix, it's in the process of being packaged.
I can confirm it only happen for file based SR when using purge snapshots.
For some reason, the vdi type of CBT_metadata is cbtlog for FileSR but stays the image format it was for LVMSR
And it would make a condition fail during thelist_changed_blockscall. -
RE: Lates commit breaks install
@acebmxer The documentations says to use Node LTS, which is currently Node v24. There may have been past issues with running on Node v24. However, AFAIK XO should build and operate fine on Node v24 now.
-
RE: Lates commit breaks install
Node v24 should work fine. The reason for your failure is here --
error eslint-visitor-keys@5.0.1: The engine "node" is incompatible with this module. Expected version "^20.19.0 || ^22.13.0 || >=24". Got "23.11.0"
Either upgrade Node to v24 or downgrade it to v22.
-
RE: Second (and final) Release Candidate for QCOW2 image format support
@abudef I don't know. I forwarded the question.
-
RE: XCP-ng 8.3 updates announcements and testing
@Andrew Hello Andrew,
Thank you for reporting.
It appear that the CBT on FileSR-based SR is not working in addition to data-destroy (the option that allow to remove the VDI content and only keep the CBT).
Can you confirm that you are using a FileSR (ext or nfs)?
Is it possible to disable purge data on the CR job? -
RE: XCP-ng 8.3 updates announcements and testing
@acebmxer Hello,
The error
VDI_CBT_ENABLEDmeans that the XAPI doesn't want to move the VDI to not break the CBT chain.
You can disable the CBT on the VDI before migrating the VDI but if you have snapshots with CBT enabled it can be complicated and it might necessitate to remove them before moving the VDI.
We have changes planned to improve the CBT handling in this kind of case.
