Bug 1652096 - If an upgrade task fails on one node, stop the upgrade on other nodes too
Summary: If an upgrade task fails on one node, stop the upgrade on other nodes too
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: z2
: 14.0 (Rocky)
Assignee: Jiri Stransky
QA Contact: Ronnie Rasouli
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-21 15:12 UTC by Jiri Stransky
Modified: 2019-04-30 17:51 UTC (History)
4 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.2.1-0.20190119154863.el7ost.noarch
Doc Type: Bug Fix
Doc Text:
This update adds an 'any_errors_fatal' setting to stop an upgrade after an upgrade task failure on any overcloud node. Prior to this update, after an upgrade failure on one overcloud node, the upgrade would continue on other overcloud nodes. Now, if an upgrade task fails on any overcloud node, the upgrade is stopped and does not progress onto next tasks on other overcloud nodes.
Clone Of:
Environment:
Last Closed: 2019-04-30 17:51:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1804468 0 None None None 2018-11-21 15:13:21 UTC
OpenStack gerrit 620320 0 None None None 2018-11-27 16:33:38 UTC
Red Hat Product Errata RHBA-2019:0878 0 None None None 2019-04-30 17:51:25 UTC

Description Jiri Stransky 2018-11-21 15:12:07 UTC 
While looking into bug 1647514 we discovered that when some upgrade task fails on one controller, the upgrade stops on that controller, but further tasks are applied on the remaining controllers. I think this is generally not desirable, we should stop the upgrade fully as soon as we hit an error.
Comment 1 Jiri Stransky 2018-11-27 16:33:38 UTC 
Master merged, backport to rocky proposed.
Comment 8 errata-xmlrpc 2019-04-30 17:51:14 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-2019:0878
Note You need to log in before you can comment on or make changes to this bug.