USHIFT-4724: Isolated tests must not have access to mirror registry

[ggiguash]

A problem was discovered with how container images were preloaded for isolated tests in bootc configurations. This led to a question on why the isolated-network.robot tests were passing. Apparently, it was due to the post-containers.cfg configuration in kickstart that opened up access to the mirror registry from the isolated VMs. The network routing to the mirror registry on the hypervisor works via the libvirt bridge IP.

This PR addresses fixes the container image embedding in the bootc configurations, adds a test for verifying no container image access from VMs and introduces a dedicated kickstart (without container configuration) for isolated tests.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-4724 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.

In response to this:

A problem was discovered with how container images were preloaded for isolated tests in bootc configurations. This led to a question on why the isolated-network.robot tests were passing. Apparently, it was due to the post-containers.cfg configuration in kickstart that opened up access to the mirror registry from the isolated VMs. The network routing to the mirror registry on the hypervisor works via the libvirt bridge IP.

This PR addresses fixes the container image embedding in the bootc configurations, adds a test for verifying no container image access from VMs and introduces a dedicated kickstart (without container configuration) for isolated tests.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[ggiguash]

/test e2e-aws-tests-periodic

[pacevedom]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ggiguash,pacevedom]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ggiguash]

/retest-required

[ggiguash]

/test e2e-aws-tests-bootc-periodic

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 15c15ba and 2 for PR HEAD bdadd1c in total

[openshift-ci]

@ggiguash: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.