Hi Markus, a Node installation is image based and this should not happen ... On an Engine system you have to call engine-setup again (don't worry) which updates installation files and then installs the versionlock'ed packages. Best regards, Oliver On 26.06.19 10:57, markus.falb@mafalb.at wrote:
Hi, I just upgraded some ovirt node 4.2.8 to ovirt node 4.3.4 After a
...snip # yum update ovirt-node-ng-image-update snap...
I rebooted, and afterwards I wanted to run a yum update like I was doing it with the previous versions, but
...snip # yum update --disableplugin fastestmirror,subscription-manager Loaded plugins: enabled_repos_upload, imgbased-persist, package_upload, product-id, search-disabled-repos, vdsmupgrade, versionlock Repository centos-sclo-rh-release is listed more than once in the configuration Excluding 76 updates due to versionlock (use "yum versionlock status" to show them) No packages marked for update Uploading Enabled Repositories Report Cannot upload enabled repos report, is this client registered? snap...
"Excluding 76 updates due to versionlock" !
Many packages are locked via the yum-versionlock plugin, also many system packages like the kernel and python (well, these 2 got my attention because there were security updates published recently). Isn't it recommended anymore to update the these packages to the latest versions? Do you use modified packages (different from CentOS?) Is it safe to remove the versionlock?
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/6QPTCDBGI4PAWJ...