Description of problem: custom display name did not change after updated on console Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-04-13-213244 How reproducible: Always Steps to Reproduce: 1. goto k8s/ns/openshift-marketplace/operators.coreos.com~v1alpha1~CatalogSource/~new to create new catalogsource Catalog source name: custom-test Display name: custom-test Publisher name: hasha Image (URL of container image): docker.io/aosqe/custom-keycloak:latest 2. goto operatehub page, check the filter under Provider Type 3. go back the yaml editor for custom-test, update the displayName to custom-test22 4. goto operatehub page, check the filter under Provider Type Actual results: 2. The display name for the new catalog source is custom-test 4. after updating, the name still is custom-test Expected results: 4. The name should be custom-test22 Additional info: oc get CatalogSource custom-test -n openshift-marketplace --output=jsonpath='{.spec.displayName}' custom-test22
Reassigning to OLM as based on my initial investigation, I believe this to be an OLM bug. In the console, all we do is display `packageManifest.status.catalogSourceDisplayName`, which doesn’t get updated when `catalogSource.spec.displayName` does.
Initial investigation shows that `packageManifest.status.catalogSourceDisplayName` is not reconciled on a constant basis but rather set once the CatalogSource is reconciled. E.g. killing the catalog pod triggers a reconcile and also updates packageManifest.status.catalogSourceDisplayName.
update displayname for existing catalosource, the operator Hub page will update the name correspondingly 4.5.0-0.nightly-2020-06-01-165039
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-2020:2409