Bug 1471720

Summary:	'openstack overcloud update ...' fails when yum is locked on an overcloud node
Product:	Red Hat OpenStack	Reporter:	Marios Andreou <mandreou>
Component:	openstack-tripleo-heat-templates	Assignee:	Marios Andreou <mandreou>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	augol, dbecker, jjoyce, jslagle, mandreou, mburns, morazi, pneedle, rhel-osp-director-maint
Target Milestone:	z4	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-5.3.0-2.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1467649
Clones:	1471721 (view as bug list)		Environment:
Last Closed:	2017-09-06 17:11:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1467649
Bug Blocks:	1471721

Description Marios Andreou 2017-07-17 10:24:55 UTC

+++ This bug was initially created as a clone of Bug #1467649 +++

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.

Comment 1 Marios Andreou 2017-07-17 10:35:12 UTC

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.

Comment 2 Marios Andreou 2017-07-20 10:56:09 UTC

merged stable/newton (see trackers above)

Comment 5 errata-xmlrpc 2017-09-06 17:11:37 UTC

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-2017:2654