On 28.06.2019, at 11:41, Oliver Riesener
<Oliver.Riesener(a)hs-bremen.de> wrote:
On 27.06.19 12:05, markus.falb(a)mafalb.at wrote:
> ...
>
> btw, on my engine I see a few versionlocks too.
>
> ...snip
> # yum versionlock list
> Loaded plugins: fastestmirror, versionlock
> ovirt-engine-webadmin-portal-4.3.4.3-1.el7.noarch
> ovirt-engine-ui-extensions-1.0.5-1.el7.noarch
> ovirt-engine-dwh-4.3.0-1.el7.noarch
> ovirt-engine-4.3.4.3-1.el7.noarch
> ovirt-engine-restapi-4.3.4.3-1.el7.noarch
> ovirt-engine-dbscripts-4.3.4.3-1.el7.noarch
> ovirt-engine-tools-backup-4.3.4.3-1.el7.noarch
> ovirt-engine-wildfly-15.0.1-1.el7.x86_64
> ovirt-engine-backend-4.3.4.3-1.el7.noarch
> ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch
> ovirt-engine-tools-4.3.4.3-1.el7.noarch
> ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7.noarch
> versionlock list done
> snap...
Your upgrade isn't complete.
At this point I would run engine-setup, it does the magic.
When I upgraded I did run engine-setup and the webinterface says it’s on version 4.3.4.
What more magic is expected?
Why do you think my upgrade is not complete?
What’s your output from a yum versionlock list ?
Best Regards, Markus