Created attachment 1683455 [details] [OCP4.5]__Create_APIcast__Red_Hat_Integration-3scale_APIcast_gateway_Operator Description of problem: The latest Operand's creation form logic in OCP 4.5 Console requires the Operand (CRD) to have a structural schema, otherwise, no fields would be rendered on Operand's creation form even with specDescritpors included in Operator's CSV file. However, due to the below reasons, OCP 4.5 Console would still need to support the existing (OCP4.3/4.4) creation form logic: OCP 4.5 is based on k8s 1.18 Only CRDs in `apiextensions.k8s.io/v1` have to have a structural schema (available since k8s 1.16) CRD in `apiextensions.k8s.io/v1beta1` structural schema is "optional" and will be deprecated in k8s 1.19 (OCP 4.6) This means for OCP 4.5 (k8s 1.18), there will be still quite a lot of CRDs still in`apiextensions.k8s.io/v1beta1` without structural schema. (e.g. Red Hat Integration - 3scale APIcast gateway Operator, APIcast Operator, Business Automation, Akka Operator etc) Version-Release number of selected component (if applicable): OCP 4.5 How reproducible: 100% Steps to Reproduce: 1. Go to 'OperatorHub' view and install "Red Hat Integration - 3scale APIcast gateway" 2. Go to 'Installed Operators' view and create "APIcast" instance Actual results: A "blank" creation form only show "Name" and "Labels" fields. Expected results: A creation form show "Name" and "Labels" fields Support the original creation form logic as in OCP 4.4 in OCP 4.5 for those CRD without structural schema. If we would like to deprecate the old logic, that could be happening alongside with CRD deprecates `apiextensions.k8s.io/v1beta1` in k8s 1.19 Additional info:
Created attachment 1683456 [details] [OCP4.4]__Create_APIcast__Red_Hat_Integration-3scale_APIcast_gateway_Operator
*** Bug 1830124 has been marked as a duplicate of this bug. ***
Created attachment 1690574 [details] 4.5 Creation Form Less Fields 1. Install Red Hat Integration - 3scale APIcast gateway(0.2.2) from Operatorhub 2. After operator is successfully installed, create APICast instance 3. Check fields on creation form, still only Name and Labels fields This is checked against 4.5.0-0.nightly-2020-05-19-041951 # oc adm release info registry.svc.ci.openshift.org/ocp/release:4.5.0-0.nightly-2020-05-19-041951 --pullspecs | grep console console quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ff55d70eb7c2698b0dd057aed8b925e4abcdaee3bf1eccd13d6004a360c49fca console-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ff45fdaaf143af841f2f84f85f4c5b0e0b03795e5a7b09a3576bdb982dd332df # oc image info quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ff55d70eb7c2698b0dd057aed8b925e4abcdaee3bf1eccd13d6004a360c49fca | grep commit io.openshift.build.commit.id=3b2eefab445187012420ff861b9e881397fdc233 io.openshift.build.commit.url=https://github.com/openshift/console/commit/3b2eefab445187012420ff861b9e881397fdc233 # git log 3b2eefab445187012420ff861b9e881397fdc233 | grep '#5287' Merge pull request #5287 from TheRealJon/1830125-bz
Created attachment 1692576 [details] reproduced on 4.5.0-0.nightly-2020-05-26-224432
Repeat the steps in https://bugzilla.redhat.com/show_bug.cgi?id=1830125#c6 This is still reproduced on 4.5.0-0.nightly-2020-05-26-224432 Attached the screenshot for refer.
Created attachment 1692579 [details] Verification screenshot
Now the fields are working on creation page. Attached the screenshot for refer. Verified on 4.5.0-0.nightly-2020-05-27-023514
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