OCPBUGS-43935: Skip run on different nodes test for SNO

[suleymanakbas91]

This test fails because there's an infrequent occurrence where a pod is in the middle of being destroyed, but it's compared to the pod coming up and both are determined to be running on the same node. Since the spirit of this test is to make sure pods are scheduled on different nodes, and there are no other nodes, it is best to skip for SNO.

[openshift-ci[bot]]

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

[openshift-ci-robot]

@suleymanakbas91: This pull request references Jira Issue OCPBUGS-43935, which is invalid:

• expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/origin/pull/29295): >This test fails because there's an infrequent occurrence where a pod is in the middle of being destroyed, but it's compared to the pod coming up and both are determined to be running on the same node. Since the spirit of this test is to make sure pods are scheduled on different nodes, and there are no other nodes, it is best to skip for SNO. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/openshift/origin/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[suleymanakbas91]

/test all

[openshift-ci[bot]]

@suleymanakbas91: 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-upgrade	02f65012f95c1d6f90bb09d9635017bbf2508125	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-agnostic-ovn-cmd	02f65012f95c1d6f90bb09d9635017bbf2508125	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-metal-ipi-ovn-ipv6	02f65012f95c1d6f90bb09d9635017bbf2508125	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-metal-ipi-ovn	02f65012f95c1d6f90bb09d9635017bbf2508125	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-openstack-ovn	02f65012f95c1d6f90bb09d9635017bbf2508125	link	false	/test e2e-openstack-ovn
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	02f65012f95c1d6f90bb09d9635017bbf2508125	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[eggfoobar]

/close

Closing for now, the issue for the skip not working on upgrade seems to be related to the upgrade command not filtering these tests. We can re-open if this is the path we want to take

[openshift-ci[bot]]

@eggfoobar: Closed this PR.

In response to [this](https://github.com/openshift/origin/pull/29295#issuecomment-2488643752): >/close > >Closing for now, the issue for the skip not working on upgrade seems to be related to the upgrade command not filtering these tests. We can re-open if this is the path we want to take Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[openshift-ci-robot]

@suleymanakbas91: This pull request references Jira Issue OCPBUGS-43935. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to [this](https://github.com/openshift/origin/pull/29295): >This test fails because there's an infrequent occurrence where a pod is in the middle of being destroyed, but it's compared to the pod coming up and both are determined to be running on the same node. Since the spirit of this test is to make sure pods are scheduled on different nodes, and there are no other nodes, it is best to skip for SNO. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.