On 27.06.19 12:05, markus.falb@mafalb.at wrote:
...
The next command makes the possible to see the locked but potential upgradable packages (up to 128).
# yum --enablerepo=base --enablerepo=updates --enablerep=extras --enablerepo=epel versionlock status
Upgrade, or not upgrade? This is the question, Didi says wait for next release. Well, with 4.1 and 4.2 I just enabled the CentOS repos and did the upgrades, there was no versionlock.
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. But I am not sure if this is a bug or feature ? Behaves of upgrade the host via cli or ui are the same.
That makes me guess that there could be some important locks on ovirt node and makes me hesitate to unconditionally disable them. I wonder how 4.3 behaves when installed on top of CentOS (not ovirt node). Engine on native Centos has exactly the Packages you have shown above versionlocked, nothing else.
best regards, oliver
Best Regards, Markus _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LZOJ63LLOO62QQ...