OTA-1585: test: Include the compressed tests binary in the CVO container image

[DavidHurta]

To make the binary discoverable to the outside world.

The following step is to register the binary in the origin repository to make the origin machine aware of the CVO tests extension.

[openshift-ci-robot]

@DavidHurta: This pull request references OTA-1585 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.21.0" version, but no target version was set.

In response to this:

To make the binary discoverable to the outside world.

The following step is to register the binary in the origin repository to make the origin machine aware of the CVO tests extension.

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

[DavidHurta]

/test images

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DavidHurta

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 [DavidHurta]

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

[DavidHurta]

Blocked by #1235.

[DavidHurta]

/test e2e-agnostic-ovn

[DavidHurta]

The e2e job failed on:

• First run:
  • : [sig-network][Feature:EgressFirewall] egressFirewall should have no impact outside its namespace [Suite:openshift/conformance/parallel]
• Second run:
  • : [sig-storage] PersistentVolumes NFS with Single PV - PVC pairs create a PV and a pre-bound PVC: test write access [Suite:openshift/conformance/parallel] [Suite:k8s]

This PR adds a new file, which is not executed anywhere, to the CVO's container image. Not likely that the flaky failures are caused by the PR.

/override ci/prow/e2e-agnostic-ovn

[openshift-ci]

@DavidHurta: Overrode contexts on behalf of DavidHurta: ci/prow/e2e-agnostic-ovn

In response to this:

The e2e job failed on:

• First run:
• : [sig-network][Feature:EgressFirewall] egressFirewall should have no impact outside its namespace [Suite:openshift/conformance/parallel]
• Second run:
• : [sig-storage] PersistentVolumes NFS with Single PV - PVC pairs create a PV and a pre-bound PVC: test write access [Suite:openshift/conformance/parallel] [Suite:k8s]

This PR adds a new file, which is not executed anywhere, to the CVO's container image. Not likely that the flaky failures are caused by the PR.

/override ci/prow/e2e-agnostic-ovn

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.

[openshift-ci]

@DavidHurta: 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.

[DavidHurta]

/verified by @DavidHurta

The changes affect only tests. The changes are not visible in the CI nor in a cluster as of the moment. I have tested the changes in combination with other relevant PRs using testwith command as mentioned in an associated PR. I believe this is sufficient.

This PR could cause some security scanning alerting to go off. However, such a change has already been done via other teams, so I presume nothing like that will happen.

[openshift-ci-robot]

@DavidHurta: This PR has been marked as verified by @DavidHurta.

In response to this:

/verified by @DavidHurta

The changes affect only tests. The changes are not visible in the CI nor in a cluster as of the moment. I have tested the changes in combination with other relevant PRs using testwith command as mentioned in an associated PR. I believe this is sufficient.

This PR could cause some security scanning alerting to go off. However, such a change has already been done via other teams, so I presume nothing like that will happen.

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.

[DavidHurta]

/cc @hongkailiu

As I am under the impression that you are interested in this area.