Bug 1828954

Summary: Creating new CR instance shows "Not found" for cluster-scoped CRs
Product: OpenShift Container Platform Reporter: Jan Safranek <jsafrane>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, jokerman, spadgett, xiaocwan
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, creating a cluster-scoped operand from the "Installed Operator" page could result in an error on submit. The form correctly creates the cluster-scoped resource.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:32:22 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
screenshot with the error
none
Created instance none

Description Jan Safranek 2020-04-28 16:22:49 UTC 
Created attachment 1682549 [details]
screenshot with the error

Version-Release number of selected component (if applicable):
Server Version: 4.5.0-0.nightly-2020-04-28-084038


How reproducible:
Always

Steps to Reproduce:
1. Install AWS EBS CSI driver operator via OLM.
Here's link to current CSV and CRD:
https://github.com/openshift/aws-ebs-csi-driver-operator/blob/0537eaf70662e05ca091b6a8102f41411a3410d1/bundle/manifests/aws-ebs-csi-driver-operator.clusterserviceversion.yaml#L1

https://github.com/openshift/aws-ebs-csi-driver-operator/blob/0537eaf70662e05ca091b6a8102f41411a3410d1/bundle/manifests/aws-csi-driver.crd.yaml#L12

Notice Scope: Cluster in the CRD.

2. On "Operator details" page, click Create Instance


3. On the create instance page, click Create in the Form view
Full URL of the page:
https://console-openshift-console.apps.jsafrane-2212.devcluster.openshift.com/k8s/ns/openshift-aws-ebs-csi-driver-operator/clusterserviceversions/aws-ebs-csi-driver-operator.v4.5.0/csi.openshift.io~v1alpha1~AWSEBSDriver/~new


Actual results:

    Error
    Fix the above errors:
        * Not Found
(see attached picture)

Expected results:

CR is created.

Additional info:

In browser console I can see these two messages:

Failed to load resource: the server responded with a status of 404 (Not Found)
https://console-openshift-console.apps.jsafrane-2212.devcluster.openshift.com/api/kubernetes/apis/csi.openshift.io/v1alpha1/namespaces/openshift-aws-ebs-csi-driver-operator/awsebsdrivers


POST https://console-openshift-console.apps.jsafrane-2212.devcluster.openshift.com/api/kubernetes/apis/csi.openshift.io/v1alpha1/namespaces/openshift-aws-ebs-csi-driver-operator/awsebsdrivers 404 (Not Found)


But the CR is not namespaced!
curl .../apis/csi.openshift.io/v1alpha1/awsebsdrivers works (and returns an empty AWSEBSDriverList). I did not test POST.
Comment 1 Jan Safranek 2020-04-28 16:25:19 UTC 
For the record: YAML view on the same page works.
Comment 4 XiaochuanWang 2020-04-30 02:47:11 UTC 
Created attachment 1683163 [details]
Created instance
Comment 5 XiaochuanWang 2020-04-30 03:14:32 UTC 
Operator instance could be successfully created by the creation form (see the screenshot)
Verified on 4.5.0-0.nightly-2020-04-29-223453
Comment 6 errata-xmlrpc 2020-07-13 17:32:22 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:2409