-
Bug
-
Resolution: Unresolved
-
Undefined
-
CNV v4.21.0, CNV v4.21.z
-
None
-
Product / Portfolio Work
-
0.42
-
False
-
-
False
-
None
-
-
CNV I/U Operators Sprint 283
-
None
Description of problem:
The get_results manifest generation in ocp-virt-validation-checkup hardcodes the nginx image to registry.redhat.io/rhel9/nginx-124:latest, ignoring the REGISTRY_SERVER parameter. This causes pod creation to
fail in disconnected environments where images must be pulled from a local/mirrored registry.
Version-Release number of selected component (if applicable):
ocp-virt-validation-checkup (current main branch)
How reproducible:
Always - occurs in any disconnected cluster environment when attempting to view results using get_results
Steps to Reproduce:
1. Set up a disconnected OpenShift Virtualization cluster with a mirrored image registry
2. Run ocp-virt-validation-checkup with TEST_SUITES configuration
3. After tests complete, generate results viewer manifests using get_results with REGISTRY_SERVER parameter:
podman run -e TIMESTAMP=${TIMESTAMP} -e REGISTRY_SERVER=<local-registry> ${OCP_VIRT_VALIDATION_IMAGE} get_results | oc apply -f -
4. Observe the created pvc-reader pod
Actual results:
The pvc-reader pod is created with ImagePullBackOff status because it attempts to pull from registry.redhat.io/rhel9/nginx-124:latest:
oc get pods -n ocp-virt-validation
NAME READY STATUS RESTARTS AGE
pvc-reader-20260127-152903 0/1 ImagePullBackOff 0 10m
The REGISTRY_SERVER parameter is ignored in the pod spec generation.
Expected results:
The pvc-reader pod should be created with the nginx image pulled from the mirrored registry specified by REGISTRY_SERVER. The pod spec should construct the image path as:
image: ${REGISTRY_SERVER}/rhel9/nginx-124:latest
or similar, using the REGISTRY_SERVER parameter to override the default Red Hat registry.
Additional info:
Impact: This completely blocks users from viewing validation checkup results in disconnected environments, as the results viewer pod cannot start.
Root cause: The get_results script/manifest template does not respect the REGISTRY_SERVER environment variable when generating the pod spec for the pvc-reader container.
Workaround: None available - users cannot view results in disconnected clusters without fixing the manifests manually.
Related: This affects the usability of ocp-virt-validation-checkup in air-gapped/disconnected environments where all container images must be mirrored to local registries.
- is triggered by
-
CNV-68306 OCP Virtualization self-certification package for Cloud providers (GA) - UI and disconnected T1
-
- In Progress
-
- links to
- mentioned on