Bug 1685066
| Summary: | [marketplace] the CSC according to the operatorsource won’t be updated when the remote registry has changed | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Fan Jia <jfan> |
| Component: | OLM | Assignee: | Aravindh Puthiyaparambil <aravindh> |
| Status: | CLOSED ERRATA | QA Contact: | Fan Jia <jfan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | aravindh, chezhang, dgoodwin, dyan, jiazha, zitang |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
Prior to f9d37cc, as part of syncing OperatorSources, the associated CatalogSourceConfigs were being deleted and recreated. This always ensured that we got the latest state from Quay. With that change we moved to updating CatalogSourceConfigs. Now in the scenario where a Quay namespace has changed without app-registry repositories being added or removed but with existing repositories being updated, these updates will not be reflected on the cluster.
Consequence: Updates from Quay are not reflected on the cluster
Fix: Drop the CatalogSourceConfig status before updating.
Result: Updates from Quay are reflected on the cluster
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:44:55 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: | |
|
Comment 2
Fan Jia
2019-03-06 06:54:47 UTC
test with the upstream image,and the function is ok now,will test when the new nightly payload is ok marketplaceimage commit:5a98c3c3c3e3482b5507ffef2c73a59f703fc10b 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 |