Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1471721 - 'openstack overcloud update ...' fails when yum is locked on an overcloud node
'openstack overcloud update ...' fails when yum is locked on an overcloud node
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
11.0 (Ocata)
All Linux
medium Severity medium
: z5
: 11.0 (Ocata)
Assigned To: Marios Andreou
Raviv Bar-Tal
: Triaged, ZStream
Depends On: 1467649 1471720
Blocks:
  Show dependency tree / graph
 
Reported: 2017-07-17 06:29 EDT by Marios Andreou
Modified: 2018-05-18 13:04 EDT (History)
10 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-6.2.7-6.el7ost
Doc Type: Enhancement
Doc Text:
In this enhancement, if a minor update is blocked by an existing yum process that prevents the package update, the process should exit with an appropriate error message. This was added because the minor update may appear to freeze, due to yum waiting for the existing yum.pid to exit; when it eventually fails it is not immediately clear why. As a result, if there is an existing yum process preventing the package update, then the minor update fails with a clear message to indicate this: "ERROR existing yum.pid detected - can't continue! Please ensure there is no other package update process for the duration of the minor update worfklow. Exiting".
Story Points: ---
Clone Of: 1471720
Environment:
Last Closed: 2018-05-18 13:02:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1704131 None None None 2017-07-17 06:29 EDT
Red Hat Knowledge Base (Solution) 3113401 None None None 2017-07-17 06:29 EDT
OpenStack gerrit 483829 None stable/ocata: MERGED tripleo-heat-templates: Adds check for existing yum process during the legacy minor update (I374eeb4164a8007ae67fea2796e... 2018-01-17 09:06 EST
OpenStack gerrit 528984 None master: MERGED tripleo-heat-templates: Check for yum lock befor all yum* operations. (I461c1c722944813493f53f339054f420d6ddbe15) 2018-01-17 09:06 EST
OpenStack gerrit 530725 None stable/ocata: MERGED tripleo-heat-templates: Check for yum lock befor all yum* operations. (I461c1c722944813493f53f339054f420d6ddbe15) 2018-01-17 09:06 EST
Red Hat Product Errata RHSA-2018:1627 None None None 2018-05-18 13:04 EDT

  None (edit)
Description Marios Andreou 2017-07-17 06:29:26 EDT 
+++ This bug was initially created as a clone of Bug #1471720 +++

+++ 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 06:35:14 EDT 
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 Lon Hohberger 2017-10-10 14:08:57 EDT 
According to our records, this should be resolved by openstack-tripleo-heat-templates-6.2.0-3.el7ost.  This build is available now.
Comment 7 Marios Andreou 2017-12-18 10:20:32 EST 
just discussed on Upgrades scrum assigning to myself for investigation
Comment 9 Marios Andreou 2017-12-19 11:44:24 EST 
yprokule posted this https://review.openstack.org/#/c/528984/ adding to trackers
Comment 10 Yurii Prokulevych 2018-01-02 07:18:34 EST 
Cherry-pick to stable/ocata added - https://review.openstack.org/#/c/530725/
Comment 28 errata-xmlrpc 2018-05-18 13:02:55 EDT 
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/RHSA-2018:1627
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.