Bug 1981882 - OLM: Missing catalog source message can be misleading
Summary: OLM: Missing catalog source message can be misleading
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Joe Caiani
QA Contact: Yadan Pei
Depends On:
TreeView+ depends on / blocked
Reported: 2021-07-13 16:06 UTC by Samuel Padgett
Modified: 2023-03-09 01:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Version: 4.8.0-0.nightly-2021-06-13-101614 Cluster ID: 8f1756d2-ca60-4189-97be-ece0a159c45b Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:89.0) Gecko/20100101 Firefox/89.0
Last Closed: 2023-03-09 01:04:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 9491 0 None open Bug 1981882: Update CatalogSource not found message 2021-07-13 16:10:39 UTC

Description Samuel Padgett 2021-07-13 16:06:43 UTC
When we can't find an operator's catalog source, we show the message "CatalogSource was removed" in a few places like the "Installed Operators" table. This message can be misleading, however, since it can appear during operator install and perhaps other times when no one has deleted a catalog source. We should replace this with a more general message like "CatalogSource not found."

Comment 2 Yadan Pei 2021-07-19 09:28:31 UTC
Hi Sam,

I'm wondering whether the logic we used to get catalogSource correct? 

When user create a global wide catalogsource and subscribe one operator into user namespace, the message `CatalogSource not found` is always there during installation early phase ~~ however I doubt if `CatalogSource not found` message is correct since the operators are coming from a global wide catalogsource and the catalogsource does exist

For example, I subscribe prometheusoperator.0.47.0 which is coming from CatalogSource 'Community Operators' in openshift-marketplace namespace, it will first show Unknown, then 'CatalogSource not found' message together with 'Cannot update'

$ oc get catalogsource -n openshift-marketplace
NAME                                    DISPLAY                          TYPE   PUBLISHER               AGE
certified-operators                     Certified Operators              grpc   Red Hat                 9h
community-operators                     Community Operators              grpc   Red Hat                 9h
custom-console-catalogsource-yanpzhan   Custom Console Testing Yanping   grpc   OpenShift QE yanpzhan   33m
redhat-marketplace                      Red Hat Marketplace              grpc   Red Hat                 9h
redhat-operators                        Red Hat Operators                grpc   Red Hat                 9h

$ oc get packagemanifest | grep prometheus
prometheus-exporter-operator                         Community Operators              9h
prometheus                                           Community Operators              9h

Comment 3 Yadan Pei 2021-07-21 10:23:51 UTC
Sam, could you help check my comment above?

Comment 4 Yadan Pei 2021-07-26 02:37:11 UTC
Assigning back for confirmation

Comment 7 Joe D'Andrea 2021-11-09 17:45:56 UTC
FWIW, IHAC trying to update rhacs-operator via the OpenShift Web Console and they're getting "Cannot Update - CatalogSource was removed" (slightly different wording, perhaps the same issue?). They're on OCP 4.7.

Here's what we know:

* By comparison, openshift-gitops was successfully updated just before trying to update rhacs-operator
* The rhacs-operator subscription shows a CatalogSource reference to redhat-operators
* The redhat-operators CatalogSource exists in openshift-marketplace
* The image referenced by redhat-operators LGTM
* Although registry.redhat.io was recently down for about 30 min, this was occurring before then
* They've never tried updating rhacs-operator before
* They are not using RHACM nor its policies on this cluster

A ticket is being filed. Meanwhile I want to add this info here in case it is of help during this BZ's investigation.

Comment 8 Jon Jackson 2021-11-23 14:38:50 UTC
Did not get a chance to fix this sprint, will address in a future sprint.

Comment 16 Shiftzilla 2023-03-09 01:04:35 UTC
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.


Note You need to log in before you can comment on or make changes to this bug.