On Wed, Feb 6, 2019 at 11:27 AM Juhani Rautiainen
<juhani.rautiainen@gmail.com> wrote:
>
> On Wed, Feb 6, 2019 at 10:31 AM Simone Tiraboschi <stirabos@redhat.com> wrote:
> >
> > The only case that could prevent that is that you are in hosted-engine mode and so you cannot set the latest host into maintenance mode without loosing the engine itself.
> >
> > If this is your case,
> > what you can do is:
> > - set HE global maintenance mode
> > - set one of the hosted-engine hosts into maintenance mode
> > - move it to a different cluster
> > - shutdown the engine VM
> > - manually restart the engine VM on the host on the custom cluster directly executing on that host: hosted-engine --vm-start
> > - connect again to the engine
> > - set all the hosts of the initial cluster into maintenance mode
> > - upgrade the cluster
> > - shut down again the engine VM
> > - manually restart the engine VM on one of the hosts of the initial cluster
> > - move back the host that got into a temporary cluster to its initial cluster
>
> I might try this one.

I tried this one and it worked. There was problem with couple of VM's
(they were made from OVA from Virtualbox). It couldn't upgrade old
cluster until they were moved to temporary cluster too (complaining
about wrong cluster level). It might have been the real reason why the
normal upgrade failed? Maybe the error message was wrong?

Thanks a lot,
Juhani