Cherry-pick a5f61ce71d1e38708c2f7bd3fc034fb5a72fd6a5 from upstream - #1935
Conversation
tryRemovingLabel() decided whether to strip the kmm.node.k8s.io/contains-modules namespace label by counting *all* Modules still present in the namespace, including sibling Modules that were themselves mid-deletion (DeletionTimestamp set, finalizer not yet removed). When several Modules in the same namespace were deleted around the same time, each one's reconcile could see its still-terminating siblings in that count and skip removing the label - while still unconditionally finalizing itself right after. Once all Modules finished terminating this way, nothing was left to ever retrigger the cleanup, leaving the label - and the namespace-deletion webhook denial - stuck permanently even though no Modules remained. Only count Modules without a DeletionTimestamp (i.e. not themselves being deleted) when deciding whether to keep the label, since a terminating sibling can't be relied on to perform the cleanup later. Upstream-Commit: a5f61ce71d1e38708c2f7bd3fc034fb5a72fd6a5
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
✅ Deploy Preview for openshift-kmm ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @github-actions[bot]. Thanks for your PR. I'm waiting for a rh-ecosystem-edge member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: github-actions[bot], TomerNewman 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 |
|
/lgtm |
|
/cherry-pick release-2.7 |
|
@TomerNewman: new pull request created: #1936 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-sigs/prow repository. |
|
/cherry-pick release-2.6 |
|
@TomerNewman: new pull request created: #1937 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-sigs/prow repository. |
|
/cherry-pick release-2.5 |
|
@TomerNewman: new pull request created: #1938 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-sigs/prow repository. |
This is an automated cherry-pick by gitstream of
a5f61ce71d1e38708c2f7bd3fc034fb5a72fd6a5fromhttps://github.com/kubernetes-sigs/kernel-module-management.Commit message:
Upstream-Commit: a5f61ce71d1e38708c2f7bd3fc034fb5a72fd6a5