XCP-ng 7.6 RC1 available
wayne last edited by
@stormi my problem isn't the bug, there always be bugs.
My problem is that there is no proper communication about it still. I think it is a serious issue about which you know before the 7.6 release as it was tested in rc phase apparently.
It should have been mentioned when 7.6 was released, so anybody be aware what they're risking with upgrading.
Anyhow, I'm glad that the fix is coming.
@wayne while it was found during the testing phase for 7.6, it was already present in 7.5 and hadn't been detected until late, so it let us assume that only few users were affected and that is was not worse to release 7.6 with it (and fix it fast) than it had been releasing 7.5 with it. We did not foresee that people still in 7.4 would skip 7.5 and discover the bug with 7.6.
That last comment is not intended as criticism of users who'd skip a release. It's just an explanation of why we thought it would not harm to release the 7.6 release as it was.
FYI The newly released xcp-emu-manager-0.0.6-2.x86_64.rpm has resolved the migration issues that i could produce.
Thanks, this is good news!
@stormi Yes it is!!
@conradical Since you had issues in 7.5 also, would you mind testing
xcp-emu-manager-0.0.3-1.2.x86_64.rpmwhich is still in the
yum install xcp-emu-manager --enablerepo='xcp-ng-updates-testing'
I don't have that pool anymore because I just yum updated it. If I get time i'll deploy 7.5 again.
olivierlambert last edited by
Yeah, the current patch is able to make it working if the load is not too huge. We are still working to get it fully functional
e it working if the load is not
I had this happen on VMs even when they had no load, but now they work. I suspect it's ignoring other progress messages that were the problem in my case.