Add el94 bootc scenarios

Author: ggiguash

test/image-blueprints/layer5-bootc/group1/rhel94-bootc-source-optionals.containerfile

@@ -0,0 +1,34 @@
+FROM localhost/rhel94-bootc-source:latest
+
+# Build arguments
+ARG PREVIOUS_MINOR_VERSION=15
+ARG USHIFT_RPM_REPO_NAME=microshift-local
+ARG USHIFT_RPM_REPO_PATH=/tmp/$USHIFT_RPM_REPO_NAME
+
+# Copy the MicroShift repository contents
+ADD $USHIFT_RPM_REPO_NAME $USHIFT_RPM_REPO_PATH
+
+# MicroShift local RPM repository
+RUN printf "\
+[microshift-local]\n\
+name=MicroShift Local Repository\n\
+baseurl=$USHIFT_RPM_REPO_PATH\n\
+enabled=1\n\
+gpgcheck=0\n\
+skip_if_unavailable=0\n" > "/etc/yum.repos.d/microshift-local.repo"
+
+# OpenShift Mirror beta RPM repository for MicroShift dependencies
+# Only the released previous minor version is guaranteed to be available
+RUN printf "\
+[openshift-mirror-beta]\n\
+name=OpenShift Mirror Beta Repository\n\
+baseurl=https://mirror.openshift.com/pub/openshift-v4/$(uname -m)/dependencies/rpms/4.${PREVIOUS_MINOR_VERSION}-el9-beta/\n\
+enabled=1\n\
+gpgcheck=0\n\
+skip_if_unavailable=0\n" > "/etc/yum.repos.d/openshift-mirror-beta.repo"
+
+# Install MicroShift optional RPMs
+RUN dnf install -y microshift-olm microshift-multus && \
+    rm -rf $USHIFT_RPM_REPO_PATH && \
+    rm -f /etc/yum.repos.d/{microshift,openshift}*.repo && \
+    dnf clean all

test/scenarios-bootc/[email protected]

@@ -0,0 +1,25 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+scenario_create_vms() {
+    prepare_kickstart host1 kickstart-bootc.ks.template rhel94-bootc-source
+    # Using centos9 is necessary for getting the latest anaconda.
+    # It is a temporary workaround until rhel-9.4.iso build is available.
+    launch_vm host1 centos9 "" "" "" "" "" "" "1"
+
+    # Open the firewall ports. Other scenarios get this behavior by
+    # embedding settings in the blueprint, but there is no blueprint
+    # for this scenario. We need 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() {
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    run_tests host1 suites/backup/backup-restore-on-reboot.robot
+}

test/scenarios-bootc/[email protected]

@@ -0,0 +1,25 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+scenario_create_vms() {
+    prepare_kickstart host1 kickstart-bootc.ks.template rhel94-bootc-source
+    # Using centos9 is necessary for getting the latest anaconda.
+    # It is a temporary workaround until rhel-9.4.iso build is available.
+    launch_vm host1 centos9 "" "" "" "" "" "" "1"
+
+    # Open the firewall ports. Other scenarios get this behavior by
+    # embedding settings in the blueprint, but there is no blueprint
+    # for this scenario. We need 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() {
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    run_tests host1 suites/backup/backups.robot
+}

test/scenarios-bootc/[email protected]

@@ -0,0 +1,25 @@
+#!/bin/bash
+
+# Sourced from cleanup_scenario.sh and uses functions defined there.
+
+scenario_create_vms() {
+    prepare_kickstart host1 kickstart-bootc.ks.template rhel94-bootc-source
+    # Using centos9 is necessary for getting the latest anaconda.
+    # It is a temporary workaround until rhel-9.4.iso build is available.
+    launch_vm host1 centos9 "" "" "" "" "" "" "1"
+
+    # Open the firewall ports. Other scenarios get this behavior by
+    # embedding settings in the blueprint, but there is no blueprint
+    # for this scenario. We need 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() {
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    run_tests host1 suites/greenboot/
+}

test/scenarios-bootc/[email protected]

@@ -0,0 +1,31 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+# NOTE: Unlike most suites, these tests rely on being run IN ORDER to
+# ensure the host is in a good state at the start of each test. We
+# could have separated them and run them as separate scenarios, but
+# did not want to spend the resources on a new VM.
+export TEST_RANDOMIZATION=none
+
+scenario_create_vms() {
+    prepare_kickstart host1 kickstart-bootc.ks.template rhel94-bootc-source
+    # Using centos9 is necessary for getting the latest anaconda.
+    # It is a temporary workaround until rhel-9.4.iso build is available.
+    launch_vm host1 centos9 "" "" "" "" "" "" "1"
+
+    # Open the firewall ports. Other scenarios get this behavior by
+    # embedding settings in the blueprint, but there is no blueprint
+    # for this scenario. We need 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() {
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    run_tests host1 suites/logscan/
+}

test/scenarios-bootc/[email protected]

@@ -0,0 +1,32 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+scenario_create_vms() {
+    prepare_kickstart host1 kickstart-bootc.ks.template rhel94-bootc-source
+    # Using centos9 is necessary for getting the latest anaconda.
+    # It is a temporary workaround until rhel-9.4.iso build is available.
+    launch_vm host1 centos9 "" "" "" "" 2 "" "1"
+
+    # Open the firewall ports. Other scenarios get this behavior by
+    # embedding settings in the blueprint, but there is no blueprint
+    # for this scenario. We need 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() {
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    local -r vmname=$(full_vm_name host1)
+    local -r vm_ip1=$("${ROOTDIR}/scripts/devenv-builder/manage-vm.sh" ip -n "${vmname}" | head -1)
+    local -r vm_ip2=$("${ROOTDIR}/scripts/devenv-builder/manage-vm.sh" ip -n "${vmname}" | tail -1)
+
+    run_tests host1 \
+        --variable "USHIFT_HOST_IP1:${vm_ip1}" \
+        --variable "USHIFT_HOST_IP2:${vm_ip2}" \
+        suites/network/multi-nic.robot
+}

test/scenarios-bootc/[email protected]

@@ -0,0 +1,31 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+# Redefine network-related settings to use the dedicated network bridge
+VM_BRIDGE_IP="$(get_vm_bridge_ip "${VM_MULTUS_NETWORK}")"
+# shellcheck disable=SC2034  # used elsewhere
+WEB_SERVER_URL="http://${VM_BRIDGE_IP}:${WEB_SERVER_PORT}"
+
+scenario_create_vms() {
+    prepare_kickstart host1 kickstart-bootc.ks.template rhel94-bootc-source-optionals
+    # Using centos9 is necessary for getting the latest anaconda.
+    # It is a temporary workaround until rhel-9.4.iso build is available.
+    # Two nics - one for macvlan, another for ipvlan (they cannot enslave the same interface)
+    launch_vm host1 centos9 "${VM_MULTUS_NETWORK}" "" "" "" "2" "" "1"
+
+    # Open the firewall ports. Other scenarios get this behavior by
+    # embedding settings in the blueprint, but there is no blueprint
+    # for this scenario. We need 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() {
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    run_tests host1 suites/optional/
+}

test/scenarios-bootc/[email protected]

@@ -0,0 +1,29 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+# Override the default test timeout of 30m
+# shellcheck disable=SC2034  # used elsewhere
+TEST_EXECUTION_TIMEOUT="1.5h"
+
+scenario_create_vms() {
+    prepare_kickstart host1 kickstart-bootc.ks.template rhel94-bootc-source
+    # Using centos9 is necessary for getting the latest anaconda.
+    # It is a temporary workaround until rhel-9.4.iso build is available.
+    launch_vm host1 centos9 "" "" "" "" "" "" "1"
+
+    # Open the firewall ports. Other scenarios get this behavior by
+    # embedding settings in the blueprint, but there is no blueprint
+    # for this scenario. We need 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() {
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    run_tests host1 suites/osconfig
+}

test/scenarios-bootc/[email protected]

@@ -0,0 +1,25 @@
+#!/bin/bash
+
+# Sourced from scenario.sh and uses functions defined there.
+
+scenario_create_vms() {
+    prepare_kickstart host1 kickstart-bootc.ks.template rhel94-bootc-source
+    # Using centos9 is necessary for getting the latest anaconda.
+    # It is a temporary workaround until rhel-9.4.iso build is available.
+    launch_vm host1 centos9 "" "" "" "" "" "" "1"
+
+    # Open the firewall ports. Other scenarios get this behavior by
+    # embedding settings in the blueprint, but there is no blueprint
+    # for this scenario. We need 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() {
+    remove_vm host1
+}
+
+scenario_run_tests() {
+    run_tests host1 suites/storage/
+}