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

[Yedidyah Bar David]

On Thu, Sep 15, 2016 at 1:58 PM, Martin Perina <mperina at redhat.com> wrote:
>
>
> On Thu, Sep 15, 2016 at 10:26 AM, Marcin M. Jessa <lists at yazzy.org> wrote:
>>
>> On 15/09/2016 10:09, Martin Perina wrote:
>>
>>> Please share setup log from /var/log/ovirt-engine/setup, exact name is
>>> printed at the end of engine-setup and usually it's the latest file.
>>> Also from which 4.0.x version are you upgrading?
>>
>>
>> The log file is attached. I was initially upgrading from 3.6 to 4.0
>> yesterday. So I was running on whatever is the latest 4.0 now.
>> 3.6 was working fine but there was no way I could import vmware guests, it
>> just failed every single time so I decided to upgrade.
>> Plus all the new, useful features of the 4.0 release.
>> But the 4.0 setup wasn't working properly, the Dashboard crashed, services
>> timed out and I had to restart Apache manually for it to even show the
>> website.
>
>
> 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. 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)?
>
> 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/
>
>
>>
>> I couldn't be bothered to start debugging and fixing it on a test setup so
>> I decided to give 4.1 a shot.
>
>
> 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.
> 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.

Not sure what's Marcin's specific problem, but please note that we have
an RFE for 4.1 to allow direct upgrades from 3.6 to 4.1 without going
through 4.0 [1]. I hardly did anything for it so far, except for adding
a jenkins job doing such an upgrades. So, Martin, if you are aware of
changes that will break this, please:

1. Help me enhance CI etc. so that we catch them sooner
2. Fix them :-)

Thanks,

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1366900

>
> Thanks
>
> Martin Perina
>
>>
>> --
>>
>> Marcin M. Jessa
>
>



-- 
Didi