-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verify matched openshift_upgrade_nodes_label #4498
Conversation
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.
aos-ci-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@sdodson this needs |
[merge][severity: blocker] |
1 similar comment
[merge][severity: blocker] |
flake on openshift/origin#14043 |
[merge][severity: blocker] |
Evaluated for openshift ansible merge up to bf97562 |
I've reviewed the test logs and the upgrade worked so i'm fine with merging this manually if it fails. The only way this would cause test failures is if it completely skipped the node upgrade and that isn't happening. |
[test]ing while waiting on the merge queue |
Evaluated for openshift ansible test up to bf97562 |
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_openshift_ansible/262/) (Base Commit: de93b27) (PR Branch Commit: bf97562) |
continuous-integration/openshift-jenkins/merge FAILURE (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_openshift_ansible/617/) (Base Commit: 96756fe) (PR Branch Commit: bf97562) (Extended Tests: blocker) |
Flake openshift/origin#13271 Driver devicemapper failed Also:
|
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.
See bug: https://bugzilla.redhat.com/show_bug.cgi?id=1457914