OLMv1 is expected to work in disconnected environments but is failing in ipv6 related jobs due to being unable to reach the network. 

As mentioned in https://redhat-internal.slack.com/archives/C01CQA76KMX/p1732125858528419?thread_ts=1732125827.452889&cid=C01CQA76KMX ipv6 jobs are run in disconnected and don't have internet access.

A link to a failed job that is impacted by this: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6-techpreview/1859160659036475392

Particular test that is impacted starts with '[sig-olmv1]'
    

4.18
    

Very. Sippy results for the job failing repeatedly https://sippy.dptools.openshift.org/sippy-ng/jobs/4.18/runs?filters=%7B%22items%22:%5B%7B%22columnField%22:%22failed_test_names%22,%22operatorValue%22:%22contains%22,%22value%22:%22%5Bsig-olmv1%5D%5BOCPFeatureGate:NewOLM%5D%20OLMv1%20Catalogs%20should%20be%20installed%20%5BSuite:openshift/conformance/parallel%5D%22%7D%5D,%22linkOperator%22:%22and%22%7D&sortField=timestamp&sort=desc
    

    1.
    2.
    3.
    

Test failed
    

Test passed
    

This may be caused by an incorrect configuration of the disconnected environment for what OLMv1 expects. Either (or both):
* There isn't an registry mapping that works for OLMv1 (likely need an ImageTagMirrorSet for registry.redhat.io)
* The catalog images were not mirrored.