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(a)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(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/6QPTCDBGI4P...

Thanks Oliver, What should not happen? That it is manually updated via yum? Hmm, always done that with previous versions. But on an my engine there are no versionlocks, and there are the ovirt repos active, I thought that updates would be picked up with an yum update. I thought that engine-setup is only for upgrades (minor and/or major version bump) Best regards, Markus

Most installed packaged are version locked. ...snip # rpm -qa|wc -l 847 # yum versionlock list|grep "^.:"|wc -l Cannot upload enabled repos report, is this client registered? 831 snap... Could you instead try an # yum versionlock list Maybe the CentOS repos are disabled by default, then versionlock status would be empty. Best Regards, Markus

On Thu, Jun 27, 2019 at 10:49 AM Oliver Riesener <Oliver.Riesener(a)hs-bremen.de&gt; wrote: If it's so urgent for you, or if you need to test something before production, you can always try latest jenkins build: https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-el7... Anyway, since 4.3 is out for some months now, I'd definitely not recommend master branch for 4.3 setups that hope for some stability (even if trying jenkins builds). I am pretty certain that it already diverted from 4.3 quite a lot. Best regards, -- Didi

How is that handled when installed on top of CentOS, not ovirt node? Best Regards, Markus

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