OCPBUGS-59627: Adding E2E test for multi-subnet featureGate

[abhay-nutanix]

Adding E2E test for multi-subnet featureGate

[openshift-ci-robot]

@abhay-nutanix: This pull request references Jira Issue OCPBUGS-59627, which is invalid:

• expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.20.z" instead

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:

Adding E2E test for multi-subnet featureGate

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.

[abhay-nutanix]

/jira refresh

[openshift-ci-robot]

@abhay-nutanix: This pull request references Jira Issue OCPBUGS-59627, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sgaoshang

In response to this:

/jira refresh

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.

[abhay-nutanix]

/retest-required

[RadekManak]

/approve
@abhay-nutanix How did you test this?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RadekManak

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

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

[abhay-nutanix]

/retest-required

[abhay-nutanix]

@RadekManak I test this out by creating a cluster with specific configuration, exporting the kubeconfig and running the test.

[damdo]

/test ?

[openshift-ci]

@damdo: The following commands are available to trigger required jobs:

/test e2e-aws-operator

/test e2e-aws-ovn

/test e2e-aws-ovn-upgrade

/test e2e-metal-ipi

/test e2e-metal-ipi-ovn-ipv6

/test e2e-metal-ipi-virtualmedia

/test goimports

/test golint

/test govet

/test images

/test okd-scos-images

/test unit

/test verify-crds-sync

/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-aws-operator-techpreview

/test e2e-azure-manual-oidc

/test e2e-azure-operator

/test e2e-azure-operator-techpreview

/test e2e-azure-ovn

/test e2e-gcp-operator

/test e2e-gcp-ovn

/test e2e-metal-ipi-ovn-dualstack

/test e2e-metal-ipi-upgrade

/test e2e-nutanix

/test e2e-openstack

/test e2e-vsphere-host-groups-ovn-techpreview

/test e2e-vsphere-operator

/test e2e-vsphere-ovn

/test e2e-vsphere-ovn-multi-vcenter

/test e2e-vsphere-ovn-serial

/test e2e-vsphere-ovn-techpreview

/test e2e-vsphere-ovn-techpreview-serial

/test e2e-vsphere-ovn-upgrade

/test e2e-vsphere-static-ovn

/test okd-scos-e2e-aws-ovn

/test regression-clusterinfra-aws-ipi-mapi

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-machine-api-operator-main-e2e-aws-operator

pull-ci-openshift-machine-api-operator-main-e2e-aws-ovn

pull-ci-openshift-machine-api-operator-main-e2e-aws-ovn-upgrade

pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi

pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-ovn-ipv6

pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-virtualmedia

pull-ci-openshift-machine-api-operator-main-goimports

pull-ci-openshift-machine-api-operator-main-golint

pull-ci-openshift-machine-api-operator-main-govet

pull-ci-openshift-machine-api-operator-main-images

pull-ci-openshift-machine-api-operator-main-okd-scos-e2e-aws-ovn

pull-ci-openshift-machine-api-operator-main-okd-scos-images

pull-ci-openshift-machine-api-operator-main-unit

pull-ci-openshift-machine-api-operator-main-verify-crds-sync

pull-ci-openshift-machine-api-operator-main-verify-deps

In response to this:

/test ?

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.

[damdo]

/hold

For e2e testing, just merged the presubimit

[damdo]

/test ?

[openshift-ci]

@damdo: The following commands are available to trigger required jobs:

/test e2e-aws-operator

/test e2e-aws-ovn

/test e2e-aws-ovn-upgrade

/test e2e-metal-ipi

/test e2e-metal-ipi-ovn-ipv6

/test e2e-metal-ipi-virtualmedia

/test goimports

/test golint

/test govet

/test images

/test okd-scos-images

/test unit

/test verify-crds-sync

/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-aws-operator-techpreview

/test e2e-azure-manual-oidc

/test e2e-azure-operator

/test e2e-azure-operator-techpreview

/test e2e-azure-ovn

/test e2e-gcp-operator

/test e2e-gcp-ovn

/test e2e-metal-ipi-ovn-dualstack

/test e2e-metal-ipi-upgrade

/test e2e-nutanix

/test e2e-nutanix-operator-multi-subnet

/test e2e-openstack

/test e2e-vsphere-host-groups-ovn-techpreview

/test e2e-vsphere-operator

/test e2e-vsphere-ovn

/test e2e-vsphere-ovn-multi-vcenter

/test e2e-vsphere-ovn-serial

/test e2e-vsphere-ovn-techpreview

/test e2e-vsphere-ovn-techpreview-serial

/test e2e-vsphere-ovn-upgrade

/test e2e-vsphere-static-ovn

/test okd-scos-e2e-aws-ovn

/test regression-clusterinfra-aws-ipi-mapi

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-machine-api-operator-main-e2e-aws-operator

pull-ci-openshift-machine-api-operator-main-e2e-aws-ovn

pull-ci-openshift-machine-api-operator-main-e2e-aws-ovn-upgrade

pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi

pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-ovn-ipv6

pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-virtualmedia

pull-ci-openshift-machine-api-operator-main-goimports

pull-ci-openshift-machine-api-operator-main-golint

pull-ci-openshift-machine-api-operator-main-govet

pull-ci-openshift-machine-api-operator-main-images

pull-ci-openshift-machine-api-operator-main-okd-scos-e2e-aws-ovn

pull-ci-openshift-machine-api-operator-main-okd-scos-images

pull-ci-openshift-machine-api-operator-main-unit

pull-ci-openshift-machine-api-operator-main-verify-crds-sync

pull-ci-openshift-machine-api-operator-main-verify-deps

In response to this:

/test ?

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.

[damdo]

/test e2e-nutanix-operator-multi-subnet

[damdo]

/hold

For e2e to pass

[damdo]

/verified by new e2e passing

[openshift-ci-robot]

@damdo: This PR has been marked as verified by [new e2e passing](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_machine-api-operator/1425/pull-ci-openshift-machine-api-operator-main-e2e-nutanix-operator-multi-subnet/1987894872912171008).

In response to this:

/verified by new e2e passing

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.

[damdo]

/unhold

[damdo]

/assign @jcpowermac

for LGTM style review

[jcpowermac]

/lgtm

[abhay-nutanix]

/retest-required

[openshift-ci]

@abhay-nutanix: 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	cac6255	link	false	/test okd-scos-e2e-aws-ovn

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.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f5cae1f and 2 for PR HEAD cac6255 in total

[openshift-ci-robot]

@abhay-nutanix: Jira Issue OCPBUGS-59627: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

• openshift/api#2415 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-59627 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

In response to this:

Adding E2E test for multi-subnet featureGate

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.