XCP-ng 7.6 RC1 available

wayne

@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.

stormi

@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.

stormi

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.

conradical

FYI The newly released xcp-emu-manager-0.0.6-2.x86_64.rpm has resolved the migration issues that i could produce.

stormi

Thanks, this is good news!

conradical

@stormi Yes it is!!

stormi

@conradical Since you had issues in 7.5 also, would you mind testing xcp-emu-manager-0.0.3-1.2.x86_64.rpm which is still in the updates_testing repository too?

yum install xcp-emu-manager --enablerepo='xcp-ng-updates-testing'

conradical

@stormi
I don't have that pool anymore because I just yum updated it. If I get time i'll deploy 7.5 again.

olivierlambert

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

conradical

@olivierlambert said in XCP-ng 7.6 RC1 available:

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.

glipschitz

This issue still appears to be present in 7.6.
It it resolved in 7.6.3? I'm reluctant to pull hosts down without being able to move VM's safely without having to stop them.

Cheers
Greg

stormi

There is no such thing as XCP-ng 7.6.3 (but there's XCP-ng Center 7.6.3). There's just XCP-ng 7.6 with latest updates applied.

The migration issues discussed above have been fixed in an update to the xcp-emu-manager package. That specific update does not require a reboot of the hosts: only a toolstack restart.

You can either apply it from Xen Orchestra, or from command line with yum update xcp-emu-manager. Then xe-toolstack-restart.

Once all hosts have the update, migration should be smooth.

stormi

Then I recommend that you apply all the other updates, but you may want to wait for one day or two because there are security fixes on their way.

stormi

Actually, looks like I had already written something about it in the Updates Howto: https://github.com/xcp-ng/xcp/wiki/Updates-Howto#a-special-word-about-xcp-ng-75-76-and-live-migrations