OPRUN-4134: Add 2 new tests for Single/Own Namespace install mode support

[camilamacedo86]

To promote a feature gate to GA, one of the required criteria is to have at least five tests covering that feature.

This PR adds two new tests for the Single/Own Namespace feature gate to increase its test coverage and help meet the GA promotion criteria.

Tests to avoid flakes - Requirement for new tests
periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial 5
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6db4eb30-a444-11f0-8c9a-d568d3d45271-0

[perdasilva]

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 5

[openshift-ci]

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/262b6a50-a386-11f0-8fc8-fe6c209e51af-0

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-4134 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 task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

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-robot]

@camilamacedo86: This pull request references OPRUN-4134 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 task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

In order to promote a feature gate to GA, one of the required criteria is to have at least five tests covering that feature.

This PR adds two new tests for the Single/Own Namespace feature gate to increase its test coverage and help meet the GA promotion criteria.

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-robot]

@camilamacedo86: This pull request references OPRUN-4134 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 task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

To promote a feature gate to GA, one of the required criteria is to have at least five tests covering that feature.

This PR adds two new tests for the Single/Own Namespace feature gate to increase its test coverage and help meet the GA promotion criteria.

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.

[camilamacedo86]

/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial 5

[openshift-ci]

@camilamacedo86: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a525a770-a42c-11f0-9fc8-d8dfbf1c5e71-0

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-4134 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 task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

To promote a feature gate to GA, one of the required criteria is to have at least five tests covering that feature.

This PR adds two new tests for the Single/Own Namespace feature gate to increase its test coverage and help meet the GA promotion criteria.

Tests to avoid flakes - Requirement for new tests

periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a525a770-a42c-11f0-9fc8-d8dfbf1c5e71-0

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]

@camilamacedo86: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3f2230e0-a5be-11f0-8b03-42a91f29dbe7-0

[bandrade]

/label qe-approved
/verified by @bandrade

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-4134 which is a valid jira issue.

Details

In response to this:

To promote a feature gate to GA, one of the required criteria is to have at least five tests covering that feature.

This PR adds two new tests for the Single/Own Namespace feature gate to increase its test coverage and help meet the GA promotion criteria.

Tests to avoid flakes - Requirement for new tests
periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial 5
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6db4eb30-a444-11f0-8c9a-d568d3d45271-0

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-robot]

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

Details

In response to this:

/label qe-approved
/verified by @bandrade

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.

[tmshort]

/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial 5

[openshift-ci]

@tmshort: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/110405a0-a60c-11f0-85ff-c88f511bac86-0

[camilamacedo86]

/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial 10

[openshift-ci]

@camilamacedo86: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/56ba6480-a617-11f0-82e9-cc96701d919b-0

[tmshort]

/lgtm
/hold
Holding until payload-aggregate runs.

[camilamacedo86]

In all aggregation tests, we can confirm that the new 2 tests passed without failures:

Issues faced in the aggregation are not related to those new testes.

P.S.: Calling it to run 10 times did not work (it was executed only 5 times, maybe because we already had an execution in progress at the time).

c/c @tmshort

[camilamacedo86]

/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial 10

[openshift-ci]

@camilamacedo86: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7cc20ef0-a809-11f0-8f58-bb64e611ce36-0

[camilamacedo86]

/hold cancel

As we discussed in the seal pod, no failures have been faced so far
The aggregation seems to have an issue that does not execute 10 times in a row
more info: #502 (comment)

[tmshort]

/hold
Because we had to do a manual sync (#519), if this goes in before the manual sync happens, the manual sync will need to be regenerated...

[camilamacedo86]

(#519) is merged now
So, I am

/hold cancel

c/c @tmshort

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a15517d and 2 for PR HEAD 80ddfb6 in total

[camilamacedo86]

/test openshift-e2e-aws

[openshift-ci]

@camilamacedo86: The following test 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/okd-scos-e2e-aws-ovn	80ddfb6	link	false	/test okd-scos-e2e-aws-ovn

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.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 1f66d6f and 1 for PR HEAD 80ddfb6 in total