Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1770903

Summary: "No Operators are available for project #ALL_NS#" appears in UI
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, jokerman, yapei
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Version: 4.3.0-0.ci-2019-11-10-053517 Cluster ID: 223bcb19-3542-4d70-9726-690f9df7f8f1
Last Closed: 2020-01-23 11:12:05 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:
Embargoed:
Attachments:
Description Flags
Incorrect empty state message for installed operators page
none
CorrectEmptyStateOnInstalledOperatorsPage none

Description Samuel Padgett 2019-11-11 13:22:27 UTC 
See screenshot. We shouldn't show "#ALL_NS#" in the message of course. In this case, I had the "default" project selected, so I wonder if there's not a more serious bug here.
Comment 1 Samuel Padgett 2019-11-11 13:22:52 UTC 
Created attachment 1634871 [details]
Incorrect empty state message for installed operators page
Comment 2 Samuel Padgett 2019-11-11 13:52:22 UTC 
This is only a problem in the empty state message itself and only a bug in 4.3.
Comment 4 Yadan Pei 2019-11-15 01:34:46 UTC 
When no installed operators for one namespace, it shows

No Operators Found
No Operators are available for project <project_name>.

Verified on   4.3.0-0.nightly-2019-11-13-233341
Comment 5 Yadan Pei 2019-11-15 01:35:42 UTC 
Created attachment 1636350 [details]
CorrectEmptyStateOnInstalledOperatorsPage
Comment 7 errata-xmlrpc 2020-01-23 11:12:05 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-2020:0062