Created attachment 1575600 [details] engine logs Description of problem: When running upgrade of host, the upgrade has failed because yum lockfile was held by another process (regular scheduled check for updates started by engine) Version-Release number of selected component (if applicable): ovirt-engine-4.3.4.2-0.1.el7.noarch How reproducible: random Steps to Reproduce: 1. run upgrade of host 2. run check for upgrade in specific time just after upgrade of ovirt-host and before update of other packages 3. Actual results: yum lockfile is held by another process Expected results: upgraded host Additional info:
There's nothing we could do about it, the same situation could for example happen by running 'yum check-update' directly at the host at the same time you execute host upgrade from UI. And writing some synchronization between check-for-upgrade and upgrade executed from engine it's just too much work for this corner case. When this happen administrators just need to run the action again
This happens always if you try to upgrade a host right after engine restart.
In Ansible 2.8 there is 'lock_timeout' for 'yum' module, which 'wait for the yum lockfile to be freed.' We can use and increase this timeout when we will use Ansible 2.8.
I wasn't able to reproduce, but I've posted a patch that should handle this
Verified on ovirt-engine-4.4.0-0.25.master.el8ev.noarch
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.