OCPEDGE-2274: fix: change arbiter topology test to verify pods do not run on arbiter nodes

[fracappa]

No description provided.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

@fracappa: This pull request references OCPEDGE-2274 which is a valid jira issue.

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]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[jaypoulz]

/hold until egli can verify that this is the right expectation for TNA + workers. I don't know if masters are schedulable on that configuration.

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fracappa, jaypoulz

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:

• test/extended/two_node/OWNERS [jaypoulz]

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

[eggfoobar]

/unhold
/payload-aggregate periodic-ci-openshift-release-master-nightly-4.22-e2e-metal-ovn-two-node-arbiter-upgrade-day-2-workers 2

Yeah this is good, masters would still be schedulable if workers get added, the user would need to update the scheduler CR to

[openshift-ci]

@eggfoobar: 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.22-e2e-metal-ovn-two-node-arbiter-upgrade-day-2-workers

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/68fafaf0-fdfc-11f0-8df8-8099a4d1afd0-0

[eggfoobar]

/payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-metal-ovn-two-node-arbiter-upgrade-day-2-workers

[openshift-ci]

@eggfoobar: 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.22-e2e-metal-ovn-two-node-arbiter-upgrade-day-2-workers

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6fae6c60-ffb9-11f0-8ac8-5cee4a8608e6-0

[eggfoobar]

/payload-job periodic-ci-openshift-release-master-nightly-4.22-upgrade-from-stable-4.21-e2e-metal-ovn-two-node-arbiter-upgrade-workers

[openshift-ci]

@eggfoobar: 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.22-upgrade-from-stable-4.21-e2e-metal-ovn-two-node-arbiter-upgrade-workers

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8c128e80-ffe7-11f0-8566-26ad3be6922d-0

[eggfoobar]

/verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30737-nightly-4.22-upgrade-from-stable-4.21-e2e-metal-ovn-two-node-arbiter-upgrade-workers/2018165158156701696

[openshift-ci-robot]

@eggfoobar: This PR has been marked as verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30737-nightly-4.22-upgrade-from-stable-4.21-e2e-metal-ovn-two-node-arbiter-upgrade-workers/2018165158156701696.

Details

In response to this:

/verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30737-nightly-4.22-upgrade-from-stable-4.21-e2e-metal-ovn-two-node-arbiter-upgrade-workers/2018165158156701696

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]

/retest-required

Remaining retests: 0 against base HEAD 2964662 and 2 for PR HEAD b86773e in total

[openshift-ci]

@fracappa: all tests passed!

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.