Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-36971

[release-4.15] Operand details page shows incorrect API version

XMLWordPrintable

    • Important
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the operand details displayed information for the first custom resource definition (CRD) that matched by name. With this release, the operand details page displays information for the CRD that matches by name and the version of the operand. (link:https://issues.redhat.com/browse/OCPBUGS-36971[*OCPBUGS-36971*])
      ____________
      Previously, the OperandDetails was displaying information for the first CRD that matched by name. After this fix, the OperandDetails page displays information for the CRD that matches by name and the version of the operand.
      Show
      * Previously, the operand details displayed information for the first custom resource definition (CRD) that matched by name. With this release, the operand details page displays information for the CRD that matches by name and the version of the operand. (link: https://issues.redhat.com/browse/OCPBUGS-36971 [* OCPBUGS-36971 *]) ____________ Previously, the OperandDetails was displaying information for the first CRD that matched by name. After this fix, the OperandDetails page displays information for the CRD that matches by name and the version of the operand.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-36841. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-34901. The following is the description of the original issue:
      —
      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:

              rhn-engineering-rhamilto Robb Hamilton
              openshift-crt-jira-prow OpenShift Prow Bot
              YaDan Pei YaDan Pei
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: