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:
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
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.
Strahil NikolovOn Oct 4, 2019 14:04, Stefano Danzi <s.danzi(a)hawai.it> wrote:
> I upgraded oVirtNode 22.214.171.124 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 126.96.36.199.
> 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
> 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
> ovirt-node-ng-image-update.noarch 0:4.3.6-1.el7
> 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: