Bug 1686668
Summary: | [marketplace] Operator Hub Removing installed operators from a custom AppRegistry results in invalid install CSC | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Sami Shahin <sashahin> |
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: | aravindh, jfan |
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:45:20 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: |
Description
Sami Shahin
2019-03-08 01:04:16 UTC
Sami, the remove of "subscription" won't delete the package in the corresponding CSC. But of course the delete of package in the remote registory should cause the CSC's Reconciling (delete the package). And I report it as https://bugzilla.redhat.com/show_bug.cgi?id=1686707, Thank you. *** Bug 1686707 has been marked as a duplicate of this bug. *** Hi Jia, I realize deleting the subscription doesn't remove a package from the CSC, just listing all my steps. :) After looking at the bug linked, I don't think this is a duplicate. The issue here isn't that the CSC isn't synced up, since I'm forcing a resync by deleting and reapplying the OperatorSource. The issue is with how the install CSC is resynced when operators are removed from the custom app registry. The bug linked notes an issue with syncing the install CSC with the app registry at all, based on my interpretation. They may be related, but the symptoms are distinct. This pr addresses the described issue: https://github.com/operator-framework/operator-marketplace/pull/138 The latest nightly build doesn't include this pr , will confirm after the pr is included by nightly build cv: 4.0.0-0.nightly-2019-03-22-002648 marketplace image:quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c802c1681883549a6a6b123719866b382218294259d55d5464415cf9464b189f marketplace commit:68b01f6507267f6deefa952a1034b74a5e8480bf (In reply to Sami Shahin from comment #3) Yes , Sami, and the bug I mentioned is fixed now. test env: cv: 4.0.0-0.nightly-2019-03-22-062943 marketplace image:quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5782d66f4f51e925a20832085e7e1457e35400543449e83c56b4213bf69725d4 marketplace commit:213899cee5dcf37f78522f56196a860be10b1e94 The csc still has the comma before the operator's name (which is the second operator installed, delete the first operator in the quay). But the csc ignore the invalid values , so the csc can be created success and the pod registory is created success. 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 |