On Thu, Nov 21, 2019 at 2:21 PM Fedor Gavrilov <fgavrilo(a)redhat.com> wrote:
Hi Nir,
Thanks for the response!
That's because the issue is about upgrading from 4.0 to, say, 4.3 when compat version
of disks has to be lazily updated.
So basically what I need to get is recent installation with an old disk, and installing
4.0 and then uprading is what reproducer suggests.
I don't think we support upgrade from 4.0 to 4.3. You need to upgrade
to 4.1 and then to 4.2,
and finally to 4.3. Adding Ryan to confirm.
What is the bug? maybe you can easily simulate by modifying engine db to trigger
an attempt to upgrade the compat version again?
Building ancient engine to reproduce a bug does not look like a good
way to spend your time.
I would do this only if there is no other way to reproduce the issue.
Nir
Fedor G
----- Original Message -----
From: "Nir Soffer" <nsoffer(a)redhat.com>
To: "Fedor Gavrilov" <fgavrilo(a)redhat.com>
Cc: "devel" <devel(a)ovirt.org>
Sent: Friday, November 15, 2019 11:22:10 PM
Subject: Re: [ovirt-devel] building ovirt-engine 4.0
On Fri, Nov 15, 2019, 19:03 Fedor Gavrilov <fgavrilo(a)redhat.com> wrote:
> Hi,
>
> To validate an issue I am working on I was trying to build ovirt-engine
> 4.0 on my CentOS 7.7 but it seems to fail for me.
>
...
> Is that how it works for everyone?
>
I don't anyone is trying to build 4.0. Why do you need it?
I think the easiest way to run older engine is to install release rpm it in
a vm running centos 7 from the time 4.0 was released.
Nir