Description of problem: 'openstack overcloud update ...' fails when yum is already locked on an overcloud node. The overcloud update subsequently times out waiting for yum_update.sh to obtain a list of packages requiring an update on that node. Version-Release number of selected component (if applicable): * Red Hat OpenStack Platform 9. * RHEL 7. * yum-3.4.3-150.el7. How reproducible: Every time. Steps to Reproduce: 1. On an overcloud node, trigger a scenario where yum is locked. In a real world use-case, this could be due to a previous issue being experienced on an overcloud node. 2. Run 'openstack overcloud update ...'. Actual results: The overcloud update times out when the yum_update.sh script tries to obtain a list of packages requiring update from the node which is locked. Expected results: For the overcloud update sequence to handle this situation effectively, perhaps through clear error messaging or by handling of the yum lock.
clones: OSP9 @ https://bugzilla.redhat.com/show_bug.cgi?id=1467649 OSP10@ https://bugzilla.redhat.com/show_bug.cgi?id=1471720 OSP11@ https://bugzilla.redhat.com/show_bug.cgi?id=1471721 No BZ needed for OSP12 since the minor update workflow there is different. However the files do still exist on master and we landed this one first https://review.openstack.org/#/c/483390/ (even though it won't be used by master/Pike) and then backported to stable/newton since that is the oldest we have right now. Will have to be d/stream for OSP9 which is what this bug was opened for in the first place. Once stable/newton merges I will post the d/stream review and attach to the OSP9 clone.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2140