Bug 1462995 - [3.5] upgrade get applied to all nodes if openshift_upgrade_nodes_label fits no label
Summary: [3.5] upgrade get applied to all nodes if openshift_upgrade_nodes_label fits ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 3.5.z
Assignee: Russell Teague
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-19 20:10 UTC by Russell Teague
Modified: 2021-12-10 15:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Verifies the provided label matches a set of hosts prior to upgrading. If the label didn't match hosts, the upgrade would silently proceed with upgrading all nodes given the logic for creating the oo_nodes_to_upgrade group.
Clone Of: 1457914
Environment:
Last Closed: 2017-06-29 13:33:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1666 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-06-29 17:32:39 UTC

Comment 1 Russell Teague 2017-06-19 20:13:01 UTC 
Proposed: https://github.com/openshift/openshift-ansible/pull/4501
Comment 2 Russell Teague 2017-06-21 17:53:20 UTC 
Merged: https://github.com/openshift/openshift-ansible/pull/4501
Comment 4 Anping Li 2017-06-27 03:02:54 UTC 
The expected message is reported, so move bug to verified.

TASK [Fail if no nodes match openshift_upgrade_nodes_label] ********************
fatal: [openshift-214.lab.eng.nay.redhat.com]: FAILED! => {
    "changed": false, 
    "failed": true
}

MSG:

openshift_upgrade_nodes_label was specified but no nodes matched
	to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_5/upgrade.retry
Comment 6 errata-xmlrpc 2017-06-29 13:33: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-2017:1666
Note You need to log in before you can comment on or make changes to this bug.