OSAC: use pruned vmaas snapshot to fix e2e disk pressure (#79304)

* OSAC: use pruned vmaas snapshot to fix e2e disk pressure

The osac-vmaas snapshot accumulated ~30 stale OLM catalog index
images (~42GB), leaving the disk at 85-86% usage on boot. This
triggered kubelet DiskPressure, preventing pod scheduling during
the refresh step and causing ~60% of e2e-vmaas runs to fail.

The pruned snapshot boots at 54% disk usage with no disk pressure.

* fix boot command to use pruned flavor name

The cluster-tool pull registers the flavor with the image tag name.
Update the boot command to match the new tag.

Author: omer-vishlitzky

ci-operator/step-registry/osac-project/cluster-tool/boot/osac-project-cluster-tool-boot-commands.sh

@@ -272,7 +272,7 @@ echo "=== Pulling OSAC vmaas flavor ==="
 python3 /usr/local/bin/cluster-tool pull "${FLAVOR_IMAGE}"
 
 echo "=== Booting cluster ==="
-python3 /usr/local/bin/cluster-tool boot --flavor osac-vmaas --name "${CLONE}"
+python3 /usr/local/bin/cluster-tool boot --flavor osac-vmaas-pruned --name "${CLONE}"
 
 systemctl restart dnsmasq
 

ci-operator/step-registry/osac-project/cluster-tool/boot/osac-project-cluster-tool-boot-ref.yaml

@@ -34,7 +34,7 @@ ref:
     default: "main"
     documentation: cluster-tool git ref to download (branch, tag, or commit)
   - name: CLUSTER_TOOL_FLAVOR_IMAGE
-    default: "quay.io/rh-ee-ovishlit/cluster-flavors:osac-vmaas"
+    default: "quay.io/rh-ee-ovishlit/cluster-flavors:osac-vmaas-pruned"
     documentation: OCI image containing the OSAC snapshot flavor
   documentation: |-
     Boots an OSAC cluster from a pre-built snapshot using cluster-tool,