Re: Recover node from partial upgrade
You can boot from the older image (grub menu) and then a cleanup procedure should be performed. I'm not sure if the thin LVs will be removed when you rerun the upgrade process , or they will remain the same. Beat Regards, Strahil NikolovOn Oct 4, 2019 14:04, Stefano Danzi <s.danzi@hawai.it> wrote:
Hello!!!
I upgraded oVirtNode 4.3.5.2 to 4.3.6 using Engine UI. In the middle of the upgrade Engine fenced it, I can't understand why.
Now Engine UI, and yum, report that there are no updates but node still to version 4.3.5.2. If I run "yum reinstall ovirt-node-ng-image-update" The result is as follow, but the system remain not upgraded.
ovirt-node-ng-image-update-4.3.6-1.el7.noarch.rpm | 719 MB 00:06:31 Running transaction check Running transaction test Transaction test succeeded Running transaction Installazione : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1 warning: %post(ovirt-node-ng-image-update-4.3.6-1.el7.noarch) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package ovirt-node-ng-image-update-4.3.6-1.el7.noarch Uploading Package Profile Cannot upload package profile. Is this client registered? Verifica in corso : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1
Installato: ovirt-node-ng-image-update.noarch 0:4.3.6-1.el7
Completo! _______________________________________________ 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/Y52X663MAR347S...
Hi! boot from older image has no effects on this issue. After long debug I figured out that after the interrupted upgrade there was two Logical volume: /dev/onn_ovirtn01/ovirt-node-ng-4.3.6-0.20190926.0 /dev/onn_ovirtn01/ovirt-node-ng-4.3.6-0.20190926.0+1 When I executed "yum reinstall ovirt-node-ng-image-update", rpm scripts try to create these LVs but fail because they already exist. So the RPM script fail with a generic error. After removing them the script completed successfully and upgrade was done. Maybe be nice if this situation will be handled correctly by installation scripts. Il 04/10/2019 17:19, Strahil ha scritto:
You can boot from the older image (grub menu) and then a cleanup procedure should be performed. I'm not sure if the thin LVs will be removed when you rerun the upgrade process , or they will remain the same.
Beat Regards, Strahil NikolovOn Oct 4, 2019 14:04, Stefano Danzi <s.danzi@hawai.it> wrote:
Hello!!!
I upgraded oVirtNode 4.3.5.2 to 4.3.6 using Engine UI. In the middle of the upgrade Engine fenced it, I can't understand why.
Now Engine UI, and yum, report that there are no updates but node still to version 4.3.5.2. If I run "yum reinstall ovirt-node-ng-image-update" The result is as follow, but the system remain not upgraded.
ovirt-node-ng-image-update-4.3.6-1.el7.noarch.rpm | 719 MB 00:06:31 Running transaction check Running transaction test Transaction test succeeded Running transaction Installazione : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1 warning: %post(ovirt-node-ng-image-update-4.3.6-1.el7.noarch) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package ovirt-node-ng-image-update-4.3.6-1.el7.noarch Uploading Package Profile Cannot upload package profile. Is this client registered? Verifica in corso : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1
Installato: ovirt-node-ng-image-update.noarch 0:4.3.6-1.el7
Completo! _______________________________________________ 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/Y52X663MAR347S...
participants (2)
-
Stefano Danzi -
Strahil