[ovirt-users] Fail to upgrade to 4.1 from 4.0

Marcin M. Jessa lists at yazzy.org
Thu Sep 15 19:50:04 UTC 2016

On 15/09/2016 12:58, Martin Perina wrote:
> ​So something went wrong on that upgrade from 3.6 to 4.0 and  it was not
> a good idea to do another upgrade when previous one went wrong.

The upgrade process went fine. The upgrade script never showed any errors.

> Anyway to confirm that could you please share with us also upgrade log between
> 3.6 and 4.0? Also how did you do the upgrade (especially what OS have
> you used on 3.6 and if upgrade was done using engine-backup or in-place)?

I backed up the installation but then I ran in-place upgrade. I was told 
on the irc I don't need to restore from backups when I'm already on 
CentOS 7. Actually failing to restore from backup brought me to the IRC 
in the first place.

I'm on CentOS Linux release 7.2.1511 (Core)
Upgrading I followed exactly the same doc you pointed to below.
Except when updating to 4.1 failed, I uninstalled everything that had to 
do with ovirt and installed the 4.0 release.

> More details about upgrade options from 3.6 to 4.0 can be found at:
> http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/
Because of that doc I installed 4.1 instead of the stable 4.0 ...

> ​So from current log I can see that upgrade from 3.6 to 4.0 was not
> successfully finished and that's why you had issues during upgrade on
> master.
Out of curiousity, where did you see that 3.6 to 4.0 update failed?

> Personaly I'd recommend you to get back into 3.6 (either by restoring
> from backup (if you performed in-place upgrade) or shutting down new
> host and starte pervious 3.6 host (if you performed upgrade using
> engine-backup) and do upgrade to 4.0 again​. And if upgrade from 3.6 to
> 4.0 is not successful, please share the logs again.

I'll try from scratch again, uninstalling everything, installing 3.6, 
restoring backups and upgrading to 4.0

I don't want to be a party popper but to be honest you need a testing 
engineer. The upgrade process is way too fragile and breaks too easily...


Marcin M. Jessa

More information about the Users mailing list