this wasn't manual but using yum update or yum reinstall. The node producing most trouble had been updated to 4.2.5-1 but I had to remove some of the LV's to get it to work. The only LV with a abrt process hanging was /dev/onn/var_log I believe but I suppose it could have been running while the fallback was trying to remove /dev/onn/ovirt-node-ng-4.2.6.1-0.20180913.0+1

We had 3 nodes that have been upgraded from 4.1.9 - 4.2.4 - 4.2.6-1 (one via 4.2.5-1)

From: Yuval Turgeman <yturgema@redhat.com>
Sent: 16 September 2018 08:24
To: Staniforth, Paul
Cc: users
Subject: Re: [ovirt-users] Re: [ANN] oVirt Engine 4.2.6 async update is now available

The failure was caused because you had /var/log LV that was not mounted for some reason (was that manual by any chance?). onn/var_crash was created during the update and removed successfully because of the var_log issue. The only question is why it didn't clean up the onn/ovirt-node-ng-4.2.6...., it failed to clean it up for some reason. Was the abrt process hanging this LV ?

Thanks,

Yuval

On Fri, Sep 14, 2018 at 11:53 AM, <p.staniforth@leedsbeckett.ac.uk> wrote:

I've managed to upgrade them now by removing logical volumes, usually it's just /dev/onn/home but one I had to keep reinstalling see were it failed so had to

lvremove /dev/onn/ovirt-node-ng-4.2.6.1-0.20180913.0+1
lvremove /dev/onn/var_crash
lvremove /dev/onn/var_log
lvremove /dev/onn/var_log_audit

I had trouble removing because failed because it was in use since there was an abrt process holding onto the mount.

Thanks,
Paul S.
_______________________________________________
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/LAS4IEPE2IF53QJVPMJEFLU2Q76AWQRD/