|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>|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2019-06-04 10:45:20 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Sami Shahin 2019-03-08 01:04:16 UTC
Comment 1 Fan Jia 2019-03-08 05:09:19 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.
Comment 2 Fan Jia 2019-03-08 05:13:39 UTC
*** Bug 1686707 has been marked as a duplicate of this bug. ***
Comment 3 Sami Shahin 2019-03-08 05:28:50 UTC
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.
Comment 4 Kevin Rizza 2019-03-21 12:36:58 UTC
This pr addresses the described issue: https://github.com/operator-framework/operator-marketplace/pull/138
Comment 5 Fan Jia 2019-03-22 03:10:37 UTC
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
Comment 6 Fan Jia 2019-03-22 11:56:31 UTC
(In reply to Sami Shahin from comment #3) Yes , Sami, and the bug I mentioned is fixed now.
Comment 7 Fan Jia 2019-03-22 12:24:38 UTC
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.
Comment 9 errata-xmlrpc 2019-06-04 10:45:20 UTC
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