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
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...
Thanks Oliver,
a Node installation is image based and this should not happen ...
What should not happen? That it is manually updated via yum? Hmm, always done that with previous versions.
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.
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
On 26.06.19 13:02, markus.falb@mafalb.at wrote:
Thanks Oliver,
a Node installation is image based and this should not happen ... What should not happen? That it is manually updated via yum? Hmm, always done that with previous versions.
I never saw version locked packages on a node before. I went from 4.2.x over previous 4.3.x versions to 4.3.4 and didn't have or see any versionlocks. What packages are locked ? # yum versionlock status Could it be a list of obsoletes ?
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. 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)
you are right on this. 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/WQCZ7MNZAGOSYJ...
On 26.06.19 13:02, markus.falb(a)mafalb.at wrote:
I never saw version locked packages on a node before. I went from 4.2.x over previous 4.3.x versions to 4.3.4 and didn't have or see any versionlocks. What packages are locked ?
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...
# yum versionlock status
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
Most installed packaged are version locked.
Ok i see. It was new for me. Thank you.
# yum versionlock list
Maybe the CentOS repos are disabled by default, then versionlock status would be empty.
Ok, the packages and versionlocks are not shown, because the were disabled by default on a ovirt node. 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. Another thing is the „oVirt Node Master - Latest master, experimental“. https://www.ovirt.org/download/node.html#ovirt-node-master---latest-master-e... Good Luck! Oliver
Best Regards, Markus
Best Regards, Oliver
_______________________________________________ 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/HYLIJZ6G6U67DM...
On Thu, Jun 27, 2019 at 10:49 AM Oliver Riesener <Oliver.Riesener@hs-bremen.de> wrote:
Most installed packaged are version locked.
Ok i see. It was new for me. Thank you.
# yum versionlock list
Maybe the CentOS repos are disabled by default, then versionlock status would be empty.
Ok, the packages and versionlocks are not shown, because the were disabled by default on a ovirt node.
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. Another thing is the „oVirt Node Master - Latest master, experimental“.
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-x8... 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,
https://www.ovirt.org/download/node.html#ovirt-node-master---latest-master-e...
Good Luck!
Oliver
Best Regards, Markus
Best Regards, Oliver
_______________________________________________ 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/HYLIJZ6G6U67DM...
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/PTWOTKNYMJZDHM...
-- Didi
...
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... 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). Best Regards, Markus
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...
On 28.06.2019, at 11:41, Oliver Riesener <Oliver.Riesener@hs-bremen.de> wrote:
On 27.06.19 12:05, markus.falb@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
Am 28.06.2019 um 11:59 schrieb Markus Falb <markus.falb@mafalb.at>:
On 28.06.2019, at 11:41, Oliver Riesener <Oliver.Riesener@hs-bremen.de> wrote:
On 27.06.19 12:05, markus.falb@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?
All fine.
Why do you think my upgrade is not complete?
Oh sorry, i mix up with yum upgrade message: # yum upgrade ... Excluding 8 updates due to versionlock (use "yum versionlock status" to show them) ...
What’s your output from a yum versionlock list ?
Same as yours. 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/EPUV3267UUFGRX...
On Wed, Jun 26, 2019 at 11:59 AM <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?
You should wait for next node release and upgrade to that. Nothing prevents you from removing lines from versionlock and running 'yum update', but I have no idea what happens on your next node upgrade - e.g. if it contains newer packages that what you manually updated, will yours take over (thus cause a downgrade), etc. If you think you really need/want to do that, experiment carefully, and if you think it's a valid need/request, please open a bug. Good luck and best regards, -- Didi
participants (4)
-
Markus Falb -
markus.falb＠mafalb.at
-
Oliver Riesener -
Yedidyah Bar David