Bug 2104340

Summary: OLM console shows "404: Not Found" instead of "No operands found" when we don't have any CR
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Management ConsoleAssignee: Rastislav Wagner <rawagner>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.11CC: cnv-qe-bugs, gouyang, rawagner, stirabos
Target Milestone: ---   
Target Release: 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-26 19:38:36 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
hpp deployment not found none

Description Guohua Ouyang 2022-07-06 02:30:13 UTC 
Description of problem:
Visit Operators -> Installed operators -> OpenShift Virtualization(openshift-cnv) -> HostPathProvisioner deployment(tab), it shows "404: Not Found" there.

In workloads -> deployment, filter "hostpath" in namespace openshift-cnv, "hostpath-provisioner-operator" is showing there.

So the cluster has hostpath-provisioner-operator installed but it shows the 404 error.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Guohua Ouyang 2022-07-06 02:31:14 UTC 
Created attachment 1894799 [details]
hpp deployment not found
Comment 3 Simone Tiraboschi 2022-07-06 09:32:23 UTC 
The user is supposed to create a CR for HPP only if needed.
but the admin console in that case should not show `404: Not Found` but `No operands found
Operands are declarative components used to define the behavior of the application.` as it was before 4.11.

Moving to Openshift console for further investigation.
Comment 4 Rastislav Wagner 2022-07-08 10:42:02 UTC 
I see the same behavior with nvidia gpu operator ClusterPolicy CRD. The issue is that the CRD is cluster scoped which console does not take into consideration and always try to fetch CR from some namespace.
Comment 5 Rastislav Wagner 2022-07-26 19:38:36 UTC 

*** This bug has been marked as a duplicate of bug 2091542 ***