Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-1372

UI: switching between the form and yaml views when installing kataconfig shows different values

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • 4.10-1.2.0, OCP 4.11
    • Operator
    • False
    • False
    • 1
    • 0
    • 0.0
    • Medium

    Description

      Description

      I've installed the osc operator in operator hub

      I go to create a KatCconfig & switch to yaml view and see:

      apiVersion: kataconfiguration.openshift.io/v1
      kind: KataConfig
      metadata:
        name: example-kataconfig
      spec:
        checkNodeEligibility: false
        kataMonitorImage: >-
          registry-proxy.engineering.redhat.com/rh-osbs/openshift-sandboxed-containers-operator-monitor:1.2.0

      I hit cancel

      I then press create again.  I'm still in yaml view and see

      kind: KataConfig
      apiVersion: kataconfiguration.openshift.io/v1
      metadata:
        name: example-kataconfig

       

      Toggling the form & back to yaml brings back the full yaml

       

      Steps to reproduce

      <What actions did you take to hit the bug?>
      1. install the osc operator
      2. click create kataconfig
      3.go to yaml view

      4. cancel creating

      5. click create kataconfig

      6. the yaml view is up &  is missing the spec: section

       

      Expected result

      To get the same yaml every time I try to create KataConfig

      Actual result

      The spec: section appears & disappears when cycling create ->cancel -> create

      Impact

      KataConfig should have a kataMonitoringImage in the example unless the user removes it from the form or yaml

      Env

      oc version
      Client Version: 4.10.0-202202160843.p0.gf93da17.assembly.stream-f93da17
      Server Version: 4.10.0-0.nightly-2022-02-16-171622
      Kubernetes Version: v1.23.3+2e8bad7

      with the qe-app-registry (stage) installed by flexy in a disconnected env.

       

      openshift sandboxed containers operator channel 1.2.0
      1.2.0-14
      oc get csv sandboxed-containers-operator.v1.2.0 -o yaml | grep sha
          containerImage: registry.redhat.io/openshift-sandboxed-containers/osc-rhel8-operator@sha256:10847165254eaee31dce6dbaa1d095853c5e82bfe878e613b010afa9ef64702a
                      image: registry.redhat.io/openshift-sandboxed-containers/osc-rhel8-operator@sha256:10847165254eaee31dce6dbaa1d095853c5e82bfe878e613b010afa9ef64702a
        - image: registry.redhat.io/openshift-sandboxed-containers/osc-rhel8-operator@sha256:10847165254eaee31dce6dbaa1d095853c5e82bfe878e613b010afa9ef64702a
        - image: registry.redhat.io/openshift-sandboxed-containers/osc-rhel8-operator@sha256:10847165254eaee31dce6dbaa1d095853c5e82bfe878e613b010afa9ef64702a

      Additional helpful info

      https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Flexy-install/77797/ built the cluster

      Attachments

        Activity

          Public project attachment banner

            context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
            current Project key: KATA

            People

              rhgkurz Greg Kurz
              tbuskey-rh Tom Buskey
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: