On Wed, Mar 1, 2017 at 3:19 PM, Chris Adams <c...@cmadams.net> wrote:
> Once upon a time, Simone Tiraboschi <stira...@redhat.com> said: > > > I recreated a 3.5 setup and upgraded the engine to 3.6 - that should > > > have been enough to import the hosted engine storage domain, right? > > > > Did you also raised the cluster compatibility level to 3.6 on the engine? > > No (I didn't realize this didn't happen until that was changed). > > However, now I'm back into the catch-22 of 3.6.7+hosted engine: the > cluster compatibility level can't be raised while there's a running VM, > and that includes the hosted engine. > Please see this one: https://bugzilla.redhat.com/show_bug.cgi?id=1364557 Simply define 'InClusterUpgrade' scheduling policy on the HE VM cluster > -- > Chris Adams <c...@cmadams.net> > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users