-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.15
-
None
Description of problem:
My CSV recently added a v1beta2 API version in addition to the existing v1beta1 version. When I create a v1beta2 CR and view it in the console, I see v1beta1 API fields and not the expected v1beta2 fields.
Version-Release number of selected component (if applicable):
4.15.14 (could affect other versions)
How reproducible:
Install 3.0.0 development version of Cryostat Operator
Steps to Reproduce:
1. operator-sdk run bundle quay.io/ebaron/cryostat-operator-bundle:ocpbugs-34901 2. cat << 'EOF' | oc create -f - apiVersion: operator.cryostat.io/v1beta2 kind: Cryostat metadata: name: cryostat-sample spec: enableCertManager: false EOF 3. Navigate to https://<openshift console>/k8s/ns/openshift-operators/clusterserviceversions/cryostat-operator.v3.0.0-dev/operator.cryostat.io~v1beta2~Cryostat/cryostat-sample 4. Observe v1beta1 properties are rendered including "Minimal Deployment" 5. Attempt to toggle "Minimal Deployment", observe that this fails.
Actual results:
v1beta1 properties are rendered in the details page instead of v1beta2 properties
Expected results:
v1beta2 properties are rendered in the details page
Additional info:
- blocks
-
OCPBUGS-36841 [release-4.16] Operand details page shows incorrect API version
-
- Closed
-
- is cloned by
-
OCPBUGS-36841 [release-4.16] Operand details page shows incorrect API version
-
- Closed
-
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update