OCPVE-723: Add optional olm fixes

[eggfoobar]

Add Support for optional OLM capability

• Add Skip annotation for OLM tests since OLM will not be running in a cluster that has capabilities set to None
• Bumped API to pull in new API change
• Moved OLM CRDs to conditionally add them when OLM is enabled

/hold
Holding for validation

[openshift-ci-robot]

@eggfoobar: This pull request references OCPVE-723 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 story to target the "4.15.0" version, but no target version was set.

Details

In response to this:

Add Support for optional OLM capability

• Add Skip annotation for OLM tests since OLM will not be running in a cluster that has capabilities set to None
• Bumped API to pull in new API change
• Moved OLM CRDs to conditionally add them when OLM is enabled

/hold
Holding for validation

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/test-infra repository.

[openshift-ci-robot]

@eggfoobar: This pull request references OCPVE-723 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 story to target the "4.15.0" version, but no target version was set.

Details

In response to this:

Add Support for optional OLM capability

• Add Skip annotation for OLM tests since OLM will not be running in a cluster that has capabilities set to None
• Bumped API to pull in new API change
• Moved OLM CRDs to conditionally add them when OLM is enabled

/hold
Holding for validation

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/test-infra repository.

[eggfoobar]

/assign @kevinrizza

Hey @kevinrizza This should be good to review, We're skipping tests for OLM, is the [sig-operator] always for OLM or should I make that more narrow?

[eggfoobar]

/unhold

@kevinrizza This should be good for final review, was able to verify no more OLM errors during no-cap CI runs. https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-launch-aws-modern/1712923427997749248

Note: the CRD Builds errors can be ignored, since they are not related to OLM and a fix will be coming shortly for them.

[bparees]

/approve
/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD d75ad27 and 2 for PR HEAD 202ba3f in total

[eggfoobar]

/retest-required

[kevinrizza]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, eggfoobar, kevinrizza

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [bparees]

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

[eggfoobar]

/retest-required

[openshift-ci]

@eggfoobar: 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-serial	202ba3f	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-openstack-ovn	202ba3f	link	false	/test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade	202ba3f	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-ovn-ipv6	202ba3f	link	false	/test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

Details

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/test-infra repository. I understand the commands that are listed here.