Created attachment 1628739 [details] 404 not found under resources Description of problem: Resources Tab under Custom Resource details page for installed operator does not list StorageClass. Instead, it gives a 404 Not Found. This is because the api request fails. Request URL: https://console-openshift-console.apps.uchapaga-oct23.devcluster.openshift.com/api/kubernetes/apis/storage.k8s.io/v1/namespaces/openshift-storage/storageclasses?limit=250 We need to use, https://console-openshift-console.apps.uchapaga-oct23.devcluster.openshift.com/api/kubernetes/apis/storage.k8s.io/v1/storageclasses?limit=250 to make request as StorageClass is not namespaced. Version-Release number of selected component (if applicable): OCP 4.2.0 How reproducible: 100% Steps to Reproduce: 1. Deploy operator 2. Create a CustomResource that owns a StorageClass 3. Check the Resource Tab for that CustomResource Actual results: 404 Not Found Expected results: List of StorageClass owned. Additional info:
It looks like we're not properly handling cluster scoped resources.
I need help reproducing Bug 1765015. Tried to install OCS but couldn't find it in the Operator Hub.
(In reply to Cyril from comment #2) > I need help reproducing Bug 1765015. Tried to install OCS but couldn't find > it in the Operator Hub. Provided a setup with error reproduced (via private chat).
I'm going to duplicate this to bug 1765009. These are different symptoms of the same basic problem. *** This bug has been marked as a duplicate of bug 1765009 ***
Removing as a duplicate since there is an additional fix needed for storage classes to work.
Umanga, can you help verify the fix? I still can't get a successful OCS operator even using release-4.2 branch. Thank you for your help
Tested with OCP 4.3.0-0.ci-2019-11-07-022944. I can see the StorageClass getting listed correctly. Attaching a screenshot and marking this as verified.
Thank you very much, umanga
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