On Fri, Jun 24, 2016 at 9:19 AM, Michal Skrivanek <mskrivan@redhat.com> wrote:
On 24 Jun 2016, at 08:15, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Fri, Jun 24, 2016 at 12:08 AM, Scott <romracer@gmail.com> wrote:
Hello list,
I've successfully upgraded oVirt to 4.0 from 3.6 on my engine and three hosts. However, it doesn't look like I can change the Cluster Compatibility Version to 4.0. It tells me I need to shut down all the VMs in the cluster. Except I use Hosted Engine. How do I change the cluster compatibility version when the engine is down?
We're on it, tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1348907 (During cluster level upgrade - warn and mark VMs as pending a configuration change when they are running)
While that’s in progress, I’m still not clear whether that is a real blocker for this flow or not as Roy/Didi was saying due to HE having it’s own separate configuration the set of hosts it runs on does not necessarily have to follow the engine’s view of the cluster. So I don’t really know what’s required for HE to change its cluster
We need a fix for the engine to allow migrating HE 3.6 to 4.0 and upgarfde of that cluster compat level - If we want to upgrade the HE cluster version the HE-VM itself must move away to a new cluster. Migrating to a new cluster is supported, but not the ChangeVmCluster action on hosted engine vm. The VM will effectively run on another host (and cluster) but the ID will remain of the old cluster. See bug https://bugzilla.redhat.com/show_bug.cgi?id=1351533 BTW, 1348907 fix won't help, cause the engine vm itself won't leave to perform this change. The engine never sees itself as starting or stopping. Thanks,
michal
Thanks in advance, Scott
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com