Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-4753

Create new RF to validate *-release-info rpm files

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Core
    • None
    • Improvement
    • 3
    • False
    • Hide

      None

      Show
      None
    • False

      Let's create new RF test cases to validate/check *-release-info rpm container images match the images in the deployed pods and verifies that images are "pullable" (without pulling them of course) just "podman inspect".

      This new RF Test Case should be added in version.robot Test Suite.

      Few example commands that may be useful:

      • Get release-info content:
        $ rpm -ql microshift-olm-release-info-4.18.0~0.nightly_2024_10_28_141654-202410290027.p0.gb172906.assembly.microshift.el9.noarch
        /usr/share/microshift/release/release-olm-aarch64.json
        /usr/share/microshift/release/release-olm-x86_64.json
      • Get container images from release-info packages:
        $ yq -r '.images.operator-lifecycle-manager' /usr/share/microshift/release/release-olm-x86_64.json
        quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5f0cc99ac3d3c81850433ba2b887eb0f3e6f677ee16b428e66619f5f94384306
      • Get container images from deployed pods:
        $ oc get pod olm-operator-646cd54bb8-b8m2l -n openshift-operator-lifecycle-manager -oyaml | yq '.spec.containers[0].image'
        quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5f0cc99ac3d3c81850433ba2b887eb0f3e6f677ee16b428e66619f5f94384306

              agullon Alejandro Gullón
              agullon Alejandro Gullón
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: