Add CNV deployment XML file

[oharan2]

Generate results file for cnv deployment individually.
PR #70723 verify changes in Openshift-Ci env.

[openshift-ci]

Hi @oharan2. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[rabin-io]

/lgtm

[rabin-io]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: oharan2, rabin-io
Once this PR has been reviewed and has the lgtm label, please assign orenc1 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[oharan2]

/test 4.13-e2e-upgrade

[openshift-ci]

@oharan2: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/test 4.13-e2e-upgrade

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.

[rabin-io]

/test e2e-deploy

[oharan2]

/retest-required

[openshift-ci]

@oharan2: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest-required

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]

New changes are detected. LGTM label has been removed.

[oharan2]

/test e2e-deploy

[openshift-ci]

@oharan2: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/test e2e-deploy

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.

[rabin-io]

/ok-to-test

[oharan2]

/remove-ok-to-test

[oharan2]

/hold

[orenc1]

closing and reopening to get changes from openshift/release#73005

[openshift-ci]

@oharan2: 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/4.14-e2e-upgrade	d094018	link	true	/test 4.14-e2e-upgrade
ci/prow/4.12-e2e-deploy	d094018	link	true	/test 4.12-e2e-deploy
ci/prow/4.14-e2e-deploy	d094018	link	true	/test 4.14-e2e-deploy
ci/prow/4.13-e2e-deploy	d094018	link	true	/test 4.13-e2e-deploy
ci/prow/4.13-e2e-upgrade	d094018	link	true	/test 4.13-e2e-upgrade
ci/prow/4.16-e2e-upgrade	d094018	link	true	/test 4.16-e2e-upgrade
ci/prow/4.16-e2e-deploy	d094018	link	true	/test 4.16-e2e-deploy
ci/prow/4.12-e2e-upgrade	d094018	link	true	/test 4.12-e2e-upgrade
ci/prow/4.21-e2e-upgrade	cbdbfd6	link	true	/test 4.21-e2e-upgrade
ci/prow/4.21-e2e-deploy	cbdbfd6	link	true	/test 4.21-e2e-deploy
ci/prow/4.21-images	cbdbfd6	link	true	/test 4.21-images
ci/prow/e2e-deploy	cbdbfd6	link	true	/test e2e-deploy
ci/prow/e2e-upgrade	cbdbfd6	link	true	/test e2e-upgrade

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