[release-4.15] OCPBUGS-48662: Fix concurrent namespace resolution#948
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: perdasilva 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 |
18e9d08 to
20c9a64
Compare
|
@perdasilva: This pull request references Jira Issue OCPBUGS-48662, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@perdasilva: This pull request references Jira Issue OCPBUGS-48662, which is invalid:
Comment 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 openshift-eng/jira-lifecycle-plugin repository. |
35348d9 to
0573f8c
Compare
|
/retest |
1 similar comment
|
/retest |
|
/label cherry-pick-approved |
|
@perdasilva: This pull request references Jira Issue OCPBUGS-48662, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
|
/jira refresh |
|
@perdasilva: This pull request references Jira Issue OCPBUGS-48662, which is valid. 7 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 openshift-eng/jira-lifecycle-plugin repository. |
Remove old CSV cleanup code Cleanup CRB/CR/MWC/VWC via finalizer. Signed-off-by: Todd Short <todd.short@me.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: f94a5edc69027aefc2f902d6b16cb849b9e18f0a
…n handler (#3483) * switch queue informer to use types.NamespacedName; relocate deletion handler Signed-off-by: Joe Lanford <joe.lanford@gmail.com> * Add error message to object count assertion failure Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> --------- Signed-off-by: Joe Lanford <joe.lanford@gmail.com> Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: edb751b9718ffe29e8462ce17867ec3db3b349ff
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
0573f8c to
8c30132
Compare
|
/retest |
|
@perdasilva: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
| queueinformer.WithLogger(op.logger), | ||
| queueinformer.WithInformer(opConditionInformer.Informer()), | ||
| queueinformer.WithSyncer(k8sSyncer), | ||
| queueinformer.WithDeletionHandler(op.handleDeletion), |
There was a problem hiding this comment.
Is this a net-new DeletionHandler for the OperatorCondition queue informer? If so, why?
There was a problem hiding this comment.
Seeing this on other queue informer setups as well. I'll keep reading :)
There was a problem hiding this comment.
Found it. The deletion handler is requeueing the owner or depending CSVs.
|
/label backport-risk-assessed |
|
@perdasilva: Jira Issue OCPBUGS-48662: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-48662 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[ART PR BUILD NOTIFIER] Distgit: operator-registry |
|
[ART PR BUILD NOTIFIER] Distgit: operator-lifecycle-manager |
This is a manual cherry-pick of #947