Re: [ovirt-users] Update engine from 4.1.5. to 4.1.6 pushes 4.1.7 for dwh
On Tue, Sep 26, 2017 at 8:01 PM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
On Tue, Sep 26, 2017 at 5:44 PM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com>
wrote:
>
> Hello,
> I'm updating my engine from 4.1.5 to 4.1.6
>
> But I see that the command
>
> # yum update "ovirt-*-setup*"
> retrieves these updates
>
> ovirt-engine-dwh-setup noarch
> 4.1.7-1.el7.centos ovirt-4.1 69 k
> ovirt-engine-setup noarch
> 4.1.6.2-1.el7.centos ovirt-4.1 9.8 k
> ovirt-engine-setup-base noarch
> 4.1.6.2-1.el7.centos ovirt-4.1 98 k
> ovirt-engine-setup-plugin-ovirt-engine noarch
> 4.1.6.2-1.el7.centos ovirt-4.1 158 k
> ovirt-engine-setup-plugin-ovirt-engine-common noarch
> 4.1.6.2-1.el7.centos ovirt-4.1 96 k
> ovirt-engine-setup-plugin-vmconsole-proxy-helper noarch
> 4.1.6.2-1.el7.centos ovirt-4.1 29 k
> ovirt-engine-setup-plugin-websocket-proxy noarch
> 4.1.6.2-1.el7.centos ovirt-4.1 27 k
> Updating for dependencies:
> ovirt-engine-lib noarch
> 4.1.6.2-1.el7.centos ovirt-4.1 31 k
>
> Is it correct the 4.1.7 version for ovirt-engine-dwh-setup?
Correct.
We built dwh 4.1.6 for oVirt 4.1.6, then needed to build again
to include another bugfix, wanted to build 4.1.6.1, but:
>
> Thanks,
> Gianluca
I found this bugzilla entry, so I updated it
https://bugzilla.redhat.com/show_bug.cgi?id=1490272
... this caused the above bug.
So we fixed the bug, but only in master branch (4.2), and
decided to bump dwh to 4.1.7.
You can see the various patches in the "External Trackers".
Note that while I do not think we had such cases in the past,
we did have many opposite ones - where dwh didn't require a new
build for some release of oVirt, so had a _lower_ version.
Best,
--
Didi