Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

wants to merge 1 commit into from

Conversation

@abhay-nutanix
Copy link

@abhay-nutanix abhay-nutanix commented Oct 31, 2025

Adding E2E test for multi-subnet featureGate

@openshift-ci openshift-ci bot requested review from mdbooth and nrb October 31, 2025 08:42
@abhay-nutanix abhay-nutanix changed the title Adding E2E test for multi-subnet featureGate OCPBUGS-59627: Adding E2E test for multi-subnet featureGate Oct 31, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 31, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 31, 2025

@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.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 31, 2025
@abhay-nutanix
Copy link
Author

abhay-nutanix commented Oct 31, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 31, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 31, 2025

@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.

@openshift-ci openshift-ci bot requested a review from sgaoshang October 31, 2025 09:05
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 31, 2025 •
edited
Loading

@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.

@abhay-nutanix
Copy link
Author

abhay-nutanix commented Nov 7, 2025

/retest-required

@RadekManak
Copy link
Contributor

RadekManak commented Nov 7, 2025

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 7, 2025

[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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 7, 2025
@abhay-nutanix
Copy link
Author

abhay-nutanix commented Nov 10, 2025

/retest-required

@abhay-nutanix
Copy link
Author

abhay-nutanix commented Nov 10, 2025

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

@damdo
Copy link
Member

damdo commented Nov 10, 2025

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 10, 2025

@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
Copy link
Member

damdo commented Nov 10, 2025

/hold

For e2e testing, just merged the presubimit

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 10, 2025
@damdo
Copy link
Member

damdo commented Nov 10, 2025

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 10, 2025

@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
Copy link
Member

damdo commented Nov 10, 2025

/test e2e-nutanix-operator-multi-subnet

@damdo
Copy link
Member

damdo commented Nov 10, 2025

/hold

For e2e to pass

@damdo
Copy link
Member

damdo commented Nov 11, 2025

/verified by new e2e passing

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 11, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 11, 2025

@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
Copy link
Member

damdo commented Nov 11, 2025

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 11, 2025
@damdo
Copy link
Member

damdo commented Nov 11, 2025

/assign @jcpowermac

for LGTM style review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mdbooth mdbooth Awaiting requested review from mdbooth

@nrb nrb Awaiting requested review from nrb

@sgaoshang sgaoshang Awaiting requested review from sgaoshang

Assignees

@jcpowermac jcpowermac

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@abhay-nutanix @openshift-ci-robot @RadekManak @damdo @jcpowermac