OPRUN-3605: sig-olmv1: update all but one of the olmv1 tests to be skipped in disconnected testing

[everettraven]

as all the skipped tests expect some level of internet access or a specific disconnected environment configuration.

[openshift-ci-robot]

@everettraven: This pull request explicitly references no jira issue.

In response to [this](https://github.com/openshift/origin/pull/29313): >as all the skipped tests expect some level of internet access or a specific disconnected environment configuration. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[joelanford]

We do expect OLMv1 to work in disconnected clusters. However it seems something is not quite configured correctly in the disconnected CI cluster. 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.

@everettraven can you open an OCPBUGS issue for this?

/lgtm /approve

[everettraven]

We do expect OLMv1 to work in disconnected clusters. However it seems something is not quite configured correctly in the disconnected CI cluster. 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.

@everettraven can you open an OCPBUGS issue for this?

/lgtm /approve

Created https://issues.redhat.com/browse/OCPBUGS-44810

[LalatenduMohanty]

/label acknowledge-critical-fixes-only

[tmshort]

You need to do a make update

[tmshort]

/lgtm

[grokspawn]

/retitle OPRUN-3605: sig-olmv1: update all but one of the olmv1 tests to be skipped in disconnected testing

[openshift-ci-robot]

@everettraven: This pull request references OPRUN-3605 which is a valid jira issue.

In response to [this](https://github.com/openshift/origin/pull/29313): >as all the skipped tests expect some level of internet access or a specific disconnected environment configuration. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[xueqzhan]

/lgtm

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, joelanford, tmshort, xueqzhan

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](https://github.com/openshift/origin/blob/master/OWNERS)~~ [xueqzhan] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[tmshort]

/retest

[grokspawn]

Note: surviving test is simply a CRD existence check, so no networking is required.

[everettraven]

/retest

[tmshort]

/retest

[everettraven]

/retest-required

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 36b577aebce6083cd4e40eb5604cb79c1c48fdc0 and 2 for PR HEAD 47e8351b18314af55e71e7e721e617dd094eb5bf in total

[everettraven]

/retest

[tmshort]

/retest

[grokspawn]

/retest

[stbenjam]

/skip

[stbenjam]

/skip

[stbenjam]

/skip

[openshift-ci[bot]]

@everettraven: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-single-node-upgrade	47e8351b18314af55e71e7e721e617dd094eb5bf	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	47e8351b18314af55e71e7e721e617dd094eb5bf	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-agnostic-ovn-cmd	47e8351b18314af55e71e7e721e617dd094eb5bf	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-openstack-ovn	47e8351b18314af55e71e7e721e617dd094eb5bf	link	false	/test e2e-openstack-ovn

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-trt[bot]]

Job Failure Risk Analysis for sha: 47e8351b18314af55e71e7e721e617dd094eb5bf

Job Name

Failure Risk

pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade

Low [sig-node] static pods should start after being created This test has passed 67.19% of 64 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week. --- [sig-node] static pods should start after being created This test has passed 67.19% of 64 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202411212037.p0.g203d2b1.assembly.stream.el9. All builds following this will include this PR.