Bug 1665021
| Summary: | [marketplace] Can’t delete operatorsource cr and catalogsourceconfig cr after deleted the subscription/csv of marketplace operator | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Fan Jia <jfan> |
| Component: | OLM | Assignee: | Kevin Rizza <krizza> |
| Status: | CLOSED ERRATA | QA Contact: | Fan Jia <jfan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | chezhang, dyan, jiazha, zitang |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:41:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
Aravindh Puthiyaparambil
2019-01-10 18:53:27 UTC
(In reply to aravindh from comment #1) > FYI, the subscription has no connection with the OperatorSource or > CatalogSourceConfig. Moreover are you sure that your cluster is not flaking > at this point? I have noticed similar issues and it usually happens when my > cluster is flaking. The cluster is ok. "delete the subscription" in the description means "delete the marketplace-operator". This is expected behavior. The marketplace operator adds finalizers to those custom resources as soon as they begin the reconciliation process. Those finalizers block the crs from being deleted until our operator is able to reconcile against the deletion phase. Then the operator will remove the finalizer and the cr will be garbage collected. So there should be no action here. change the stauts to verified by this is the expected behavior. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758 |