Le 12-Feb-2018 08:06:43 +0100, jbelka@redhat.com a écrit:

> This option relevant only for the upgrade from 3.6 to 4.0(engine had
> different OS major versions), it all other cases the upgrade flow very
> similar to upgrade flow of standard engine environment.
>
>
> 1. Put hosted-engine environment to GlobalMaintenance(you can do it via
> UI)
> 2. Update engine packages(# yum update -y)
> 3. Run engine-setup
> 4. Disable GlobalMaintenance
>

 

So I followed these steps connected in the engine VM and didn't get any error message. But the version showed in the GUI is

still 4.2.0.2-1.el7.centos. Yum had no newer packages to install. And I still have the "no default route" and network validation problems.

Regards

> Could someone explain me at least what "Cluster PROD is at version 4.2 which
> is not supported by this upgrade flow. Please fix it before upgrading."
> means ? As far as I know 4.2 is the most recent branch available, isn't it ?

I have no idea where did you get

"Cluster PROD is at version 4.2 which is not supported by this upgrade flow. Please fix it before upgrading."

Please do not cut output and provide exact one.

IIUC you should do 'yum update ovirt\*setup\*' and then 'engine-setup'
and only after it would finish successfully you would do 'yum -y update'.
Maybe that's your problem?

Jiri

---

FreeMail powered by mail.fr

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users