[release-4.14] OCPBUGS-22984: Introduce upgrading label to block concurrent upgrades #1926
Conversation
This change introduces the concept of maximum number of parallel upgrades that takes place concurrently for Windows nodes during reconciliation. The `windowsmachineconfig.openshift.io/upgrading` label is proposed as the locking mechanism among the Windows nodes to account for how many instances can perform an upgrade under following a threshold i.e. MaxParallelUpgrades which is fixed to 1. (cherry picked from commit f1dd8f5)
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
openshift-ci-robot
added
jira/severity-important
|
@jrvaldes: This pull request references Jira Issue OCPBUGS-22984, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/jira refresh |
|
@jrvaldes: This pull request references Jira Issue OCPBUGS-22984, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/test ? |
|
@jrvaldes: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/jira ? |
|
/test vsphere-e2e-upgrade |
|
vsphere-e2e-upgrade failed with |
This commit introduces a test to check the maximum allowed numbers of Windows nodes upgrading in parallel. The test is divided in two phases, 1) setup and 2) test, where the setup phase deploys a job with a fixed name that constantly fetch the number of Windows nodes with the `windowsmachineconfig.openshift.io/upgrading` label and fail if is greater than the maximum allowed. The polling frequency is set to 5 seconds. The latter test, checks the number of failed pods for the checker job and require no failures, otherwise fails the e2e test. A new service account is proposed in the test namespace to hold the RBAC required by the checker job to list the nodes in the test cluster. The test is designed to run as a separate job due to the structure of the new upgrade test in vSphere (vsphere-e2e-upgrade) that is scattered between the steps in the release repo and code in the WMCO test suite. (cherry picked from commit e03c792)
This changes aggregates the RBAC resources required by the test runner job in the proposed function ensureTestRunnerRBAC() to avoid duplication of intended functionality. (cherry picked from commit a2a6f6b)
jrvaldes
force-pushed
the
release-4.14-backport-1901
branch
from
a367e19
to
1fffa07
Compare
|
/test vsphere-e2e-upgrade |
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@jrvaldes: This pull request references Jira Issue OCPBUGS-22984, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/jira refresh |
|
@jrvaldes: This pull request references Jira Issue OCPBUGS-22984, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
/unassign |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
/hold cancel |
|
/lgtm |
|
@jrvaldes: you cannot LGTM your own PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
|
/retest-required |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jrvaldes, sebsoto The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@jrvaldes: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
openshift-merge-bot
bot
merged commit 124be2f
into
openshift:release-4.14
|
@jrvaldes: Jira Issue OCPBUGS-22984: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-22984 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is a manual cherry-pick of #1901