add 2 new scenarios to test latest released bootc image available from mirror.openshift.com repo

Author: agullon

test/bin/common_versions.sh

@@ -147,12 +147,19 @@ export BREW_Y2_RELEASE_VERSION
 export BREW_RC_RELEASE_VERSION
 export BREW_EC_RELEASE_VERSION
 
-# Set the release type to ec, rc or zstream
-LATEST_RELEASE_TYPE="ec"
+# Latest Release info
+LATEST_RELEASE_TYPE="ec" # ec, rc or zstream
+BREW_LREL_RELEASE_VERSION="${BREW_EC_RELEASE_VERSION}" # BREW_EC_RELEASE_VERSION, BREW_RC_RELEASE_VERSION or BREW_Y0_RELEASE_VERSION
+LATEST_RELEASE_VERSION="$(echo "${BREW_LREL_RELEASE_VERSION}" | sed -E 's/(.*)-.*/\1/' | sed -E 's/(.*)~(.*)/\1-\2/')" # example: 4.19.7 or 4.20.0-rc.3
+if [[ "${LATEST_RELEASE_TYPE}" == "ec" ]]; then
+    KONFLUX_LREL_RELEASE_IMAGE_URL="https://mirror.openshift.com/pub/openshift-v4/$(uname -m)/microshift/ocp-dev-preview/${LATEST_RELEASE_VERSION}/el9/bootc-pullspec.txt"
+else
+    KONFLUX_LREL_RELEASE_IMAGE_URL="https://mirror.openshift.com/pub/openshift-v4/$(uname -m)/microshift/ocp/${LATEST_RELEASE_VERSION}/el9/bootc-pullspec.txt"
+fi
 export LATEST_RELEASE_TYPE
-
-BREW_LREL_RELEASE_VERSION="${BREW_EC_RELEASE_VERSION}"
 export BREW_LREL_RELEASE_VERSION
+export LATEST_RELEASE_VERSION
+export KONFLUX_LREL_RELEASE_IMAGE_URL
 
 # Branch and commit for the openshift-tests-private repository
 OPENSHIFT_TESTS_PRIVATE_REPO_BRANCH="release-4.${MINOR_VERSION}"

test/scenarios-bootc/releases/[email protected]

@@ -0,0 +1,48 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+# Enable container signature verification for published MicroShift images.
+# These are ec / rc / z-stream, thus guaranteed to be signed.
+# shellcheck disable=SC2034  # used elsewhere
+IMAGE_SIGSTORE_ENABLED=true
+
+scenario_create_vms() {
+    if [[ "${KONFLUX_LREL_RELEASE_IMAGE_URL}" == "" ]] ; then
+        # Empty string means there's no bootc image build yet, so the test needs to be skipped.
+        exit 0
+    fi
+
+    local -r bootc_spec="$(curl -s "${KONFLUX_LREL_RELEASE_IMAGE_URL}")"
+    if [ -z "${bootc_spec}" ] || [[ "${bootc_spec}" != quay.io/openshift* ]] ; then
+        echo "ERROR: Failed to retrieve a bootc pull spec from '${KONFLUX_LREL_RELEASE_IMAGE_URL}'"
+        exit 1
+    fi
+    prepare_kickstart host1 kickstart-bootc.ks.template "${bootc_spec}"
+    launch_vm --boot_blueprint rhel96-bootc
+
+    # Open the firewall ports. Other scenarios get this behavior by embedding
+    # settings in the blueprint, but we cannot open firewall ports in published
+    # images. We need to do this step before running the RF suite so that suite
+    # can assume it can reach all of the same ports as for any other test.
+    configure_vm_firewall host1
+}
+
+scenario_remove_vms() {
+    if [[ "${CURRENT_RELEASE_REPO}" == "" ]] ; then
+        # Empty string means there's no EC build yet, so the test needs to be skipped.
+        exit 0
+    fi
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    if [[ "${CURRENT_RELEASE_REPO}" == "" ]] ; then
+        # Empty string means there's no EC build yet, so the test needs to be skipped.
+        exit 0
+    fi
+    run_tests host1 \
+        --variable "EXPECTED_OS_VERSION:9.6" \
+        --variable "IMAGE_SIGSTORE_ENABLED:True" \
+        suites/standard1/ suites/selinux/validate-selinux-policy.robot
+}

test/scenarios-bootc/releases/[email protected]

@@ -0,0 +1,47 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+# Enable container signature verification for published MicroShift images.
+# These are ec / rc / z-stream, thus guaranteed to be signed.
+# shellcheck disable=SC2034  # used elsewhere
+IMAGE_SIGSTORE_ENABLED=true
+
+scenario_create_vms() {
+    if [[ "${KONFLUX_LREL_RELEASE_IMAGE_URL}" == "" ]] ; then
+        # Empty string means there's no bootc image build yet, so the test needs to be skipped.
+        exit 0
+    fi
+
+    local -r bootc_spec="$(curl -s "${KONFLUX_LREL_RELEASE_IMAGE_URL}")"
+    if [ -z "${bootc_spec}" ] || [[ "${bootc_spec}" != quay.io/openshift* ]] ; then
+        echo "ERROR: Failed to retrieve a bootc pull spec from '${KONFLUX_LREL_RELEASE_IMAGE_URL}'"
+        exit 1
+    fi
+    prepare_kickstart host1 kickstart-bootc.ks.template "${bootc_spec}"
+    launch_vm --boot_blueprint rhel96-bootc
+
+    # Open the firewall ports. Other scenarios get this behavior by embedding
+    # settings in the blueprint, but we cannot open firewall ports in published
+    # images. We need to do this step before running the RF suite so that suite
+    # can assume it can reach all of the same ports as for any other test.
+    configure_vm_firewall host1
+}
+
+scenario_remove_vms() {
+    if [[ "${CURRENT_RELEASE_REPO}" == "" ]] ; then
+        # Empty string means there's no EC build yet, so the test needs to be skipped.
+        exit 0
+    fi
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    if [[ "${CURRENT_RELEASE_REPO}" == "" ]] ; then
+        # Empty string means there's no EC build yet, so the test needs to be skipped.
+        exit 0
+    fi
+    run_tests host1 \
+        --variable "IMAGE_SIGSTORE_ENABLED:True" \
+        suites/standard2/
+}