Bug 1978376: Add admin ack Upgradeable condition gate#633
Bug 1978376: Add admin ack Upgradeable condition gate#633openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
|
@jottofar: This pull request references Bugzilla bug 1978376, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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. |
8a1297d to
abc4ce7
Compare
44e9edf to
457b720
Compare
|
/hold |
f92559c to
a34c588
Compare
ea2f404 to
ad746a8
Compare
|
/unhold |
094458b to
f30aedb
Compare
f30aedb to
519b466
Compare
|
Tightened up gate regex to require one and only one following dash followed by something, i.e. the description. Changed error message to simply spit out "must comply with" and the regex expression itself since it's too hard to explain and these errors should only be consumed by developers. If an admin does add a gate in the field I don't think it's too much to ask that they understand regex. |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jottofar, LalatenduMohanty, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The update job had terrible API-server / ingress connectivity. That's being tracked in rhbz#1955333 and/or rhbz#1997057, and is orthogonal to this PR, so: /override ci/prow/e2e-agnostic-upgrade |
|
@wking: Overrode contexts on behalf of wking: ci/prow/e2e-agnostic-upgrade DetailsIn 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. |
|
@jottofar: All pull requests linked via external trackers have merged: Bugzilla bug 1978376 has been moved to the MODIFIED state. DetailsIn 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. |
519b466 (Bug 1978376: Add admin ack Upgradeable condition gate, 2021-07-27, openshift#633) had these commented out, because 4.9 has no built-in acks. But with the code commented out, it's hard to verify that the logic works in 4.9 before backporting to 4.8 [1]. Enabling these checks should be a no-op outside of verification, because admins are unlikely to inject additional keys in the openshift-config-managed namespace's admin-gates ConfigMap. And it allows us to verify the logic in 4.9 and cook there with live code before approving the 4.8 backports. It's also one less thing we might forget before enabling new admin acks in future versions, like 4.10 or later. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1978376#c19
|
/cherry-pick release-4.8 |
|
@jottofar: #633 failed to apply on top of branch "release-4.8": DetailsIn 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 PR adds a generic upgrade blocking mechanism for blocking minor level upgrades. It is the general implementation of the Add admin ack upgrade gate enhancement. Therefore since 4.9 does not contain any active admin ack gates the check
clusterAdminAcksCompletedUpgradeableis not added todefaultUpgradeableChecks. It is added as part of unit test and tested.This PR will be backported to 4.8.z and the 4.8 specific implementation details will be added, i.e. the
ack-4.8-kube-122-api-removals-in-4.9gate will be added by adding checkclusterAdminAcksCompletedUpgradeabletodefaultUpgradeableChecks.Once active the
clusterAdminAcksCompletedUpgradeableUpgradeable check implementation differs from other Upgradeable checks by also being synchronously triggered when either configmap admin-gates or admin-acks is added, updated, or deleted. This will be achieved by adding an event handler to thecmConfigInformerandcmConfigManagedInformerInformers. The event handlers will simply invokesetUpgradeableConditionsto ensure all conditions are properly evaluated. Since the check will be added as a default Upgradeable check when active it will also be evaluated during the existing periodic polling of Upgradeable conditions.I also removed the unused parameter
configfromcvo.syncUpgradeable.