Skip to content

SPLAT-2060: Create e2e tests for vSphere Data Disk feature#1338

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
vr4manta:test-ext-framework
Mar 13, 2025
Merged

SPLAT-2060: Create e2e tests for vSphere Data Disk feature#1338
openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
vr4manta:test-ext-framework

Conversation

@vr4manta
Copy link
Copy Markdown
Contributor

@vr4manta vr4manta commented Mar 5, 2025

SPLAT-2060

Changes

  • Created new external test extension to origin
  • Added e2e tests for vSphere data disks

Blocks

Notes

After this merges, we will need to update origin to register this extension so it runs in future e2e tests.

This enhancment is leveraging the following origin framework enhancement: openshift/enhancements#1676

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Mar 5, 2025

@vr4manta: This pull request references SPLAT-2060 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 story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

SPLAT-2060

Changes

  • Created new external test extension to origin
  • Added e2e tests for vSphere data disks

Notes

After this merges, we will need to update origin to register this extension so it runs in future e2e tests.

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 5, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Mar 5, 2025

@vr4manta: This pull request references SPLAT-2060 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 story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

SPLAT-2060

Changes

  • Created new external test extension to origin
  • Added e2e tests for vSphere data disks

Notes

After this merges, we will need to update origin to register this extension so it runs in future e2e tests.

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 review from damdo and racheljpg March 5, 2025 13:55
@vr4manta vr4manta force-pushed the test-ext-framework branch from 0aea6f0 to 5e45dd2 Compare March 5, 2025 14:59
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Mar 5, 2025

@vr4manta: This pull request references SPLAT-2060 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 story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

SPLAT-2060

Changes

  • Created new external test extension to origin
  • Added e2e tests for vSphere data disks

Blocks

Notes

After this merges, we will need to update origin to register this extension so it runs in future e2e tests.

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.

@vr4manta vr4manta force-pushed the test-ext-framework branch from 5e45dd2 to 053cdde Compare March 5, 2025 19:53
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 7, 2025
@vr4manta vr4manta force-pushed the test-ext-framework branch from 053cdde to 47ba220 Compare March 10, 2025 11:36
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 10, 2025
@vr4manta vr4manta force-pushed the test-ext-framework branch from 47ba220 to c1ff7ce Compare March 10, 2025 11:40
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Mar 10, 2025

@vr4manta: This pull request references SPLAT-2060 which is a valid jira issue.

Details

In response to this:

SPLAT-2060

Changes

  • Created new external test extension to origin
  • Added e2e tests for vSphere data disks

Blocks

Notes

After this merges, we will need to update origin to register this extension so it runs in future e2e tests.

This enhancment is leveraging the following origin framework enhancement: openshift/enhancements#1676

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.

@vr4manta
Copy link
Copy Markdown
Contributor Author

/assign @JoelSpeed

Comment thread cmd/machine-api-tests-ext/main.go Outdated
Comment thread cmd/machine-api-tests-ext/main.go Outdated
Comment on lines +67 to +68
// If test has vsphere in title, make sure its only run on platform=vsphere
specs.Select(extensiontests.NameContains("[platform:vsphere]")).
Include(extensiontests.PlatformEquals("vsphere"))
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh interesting, should we do this generically for all platforms?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so. This was my way of making sure it works. I am just an e2e rookie so this is what was working for me. It did help me find a bug w/ openshift-test binary that injects --platform=skeleton whenever --dry-run is used. Would you like me to update this to strip out the platform type and dynamically inject it into equals clause?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah if it's possible/easy to make this generic for all platforms now, that would be helpful for the future I think

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JoelSpeed I took a stab at dynamically going through all tests and adding each platform specific rule for tests with first occurrence of a new platform. Thoughts?

Comment thread cmd/machine-api-tests-ext/provider.go Outdated
Comment thread test/e2e/util.go Outdated
Comment thread test/e2e/vsphere/machines.go Outdated
Comment thread test/e2e/vsphere/machines.go
Comment thread test/e2e/vsphere/machines.go Outdated
@vr4manta vr4manta force-pushed the test-ext-framework branch 2 times, most recently from ceb3a7f to 61fb64d Compare March 12, 2025 14:32
@vr4manta vr4manta force-pushed the test-ext-framework branch from 61fb64d to e117e81 Compare March 12, 2025 14:41
@JoelSpeed
Copy link
Copy Markdown
Contributor

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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:

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 Mar 12, 2025
@rvanderp3
Copy link
Copy Markdown
Contributor

/retest-required

@rvanderp3
Copy link
Copy Markdown
Contributor

/test yaml-lint

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 56773e1 and 2 for PR HEAD e117e81 in total

1 similar comment
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 56773e1 and 2 for PR HEAD e117e81 in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 56773e1 and 2 for PR HEAD e117e81 in total

@hector-vido
Copy link
Copy Markdown

/test yaml-lint

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 12, 2025

@hector-vido: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-aws-operator
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade
/test goimports
/test golint
/test govet
/test images
/test okd-scos-images
/test security
/test unit
/test verify-crds-sync

The following commands are available to trigger optional jobs:

/test e2e-azure-manual-oidc
/test e2e-azure-operator
/test e2e-azure-ovn
/test e2e-gcp-operator
/test e2e-gcp-ovn
/test e2e-metal-ipi
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-upgrade
/test e2e-metal-ipi-virtualmedia
/test e2e-nutanix
/test e2e-openstack
/test e2e-vsphere-operator
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-multi-vcenter
/test e2e-vsphere-ovn-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-azure-operator
pull-ci-openshift-machine-api-operator-main-e2e-azure-ovn
pull-ci-openshift-machine-api-operator-main-e2e-gcp-operator
pull-ci-openshift-machine-api-operator-main-e2e-gcp-ovn
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-ovn-dualstack
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-upgrade
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-virtualmedia
pull-ci-openshift-machine-api-operator-main-e2e-nutanix
pull-ci-openshift-machine-api-operator-main-e2e-openstack
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-operator
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-multi-vcenter
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-serial
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-upgrade
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-static-ovn
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-regression-clusterinfra-aws-ipi-mapi
pull-ci-openshift-machine-api-operator-main-security
pull-ci-openshift-machine-api-operator-main-unit
pull-ci-openshift-machine-api-operator-main-verify-crds-sync
Details

In response to this:

/test yaml-lint

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.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 56773e1 and 2 for PR HEAD e117e81 in total

@deepsm007
Copy link
Copy Markdown

/test yaml-lint

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 13, 2025

@deepsm007: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-aws-operator
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade
/test goimports
/test golint
/test govet
/test images
/test okd-scos-images
/test security
/test unit
/test verify-crds-sync

The following commands are available to trigger optional jobs:

/test e2e-azure-manual-oidc
/test e2e-azure-operator
/test e2e-azure-ovn
/test e2e-gcp-operator
/test e2e-gcp-ovn
/test e2e-metal-ipi
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-upgrade
/test e2e-metal-ipi-virtualmedia
/test e2e-nutanix
/test e2e-openstack
/test e2e-vsphere-operator
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-multi-vcenter
/test e2e-vsphere-ovn-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-azure-operator
pull-ci-openshift-machine-api-operator-main-e2e-azure-ovn
pull-ci-openshift-machine-api-operator-main-e2e-gcp-operator
pull-ci-openshift-machine-api-operator-main-e2e-gcp-ovn
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-ovn-dualstack
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-upgrade
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-virtualmedia
pull-ci-openshift-machine-api-operator-main-e2e-nutanix
pull-ci-openshift-machine-api-operator-main-e2e-openstack
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-operator
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-multi-vcenter
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-serial
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-upgrade
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-static-ovn
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-regression-clusterinfra-aws-ipi-mapi
pull-ci-openshift-machine-api-operator-main-security
pull-ci-openshift-machine-api-operator-main-unit
pull-ci-openshift-machine-api-operator-main-verify-crds-sync
Details

In response to this:

/test yaml-lint

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.

@JoelSpeed
Copy link
Copy Markdown
Contributor

/override ci/prow/yaml-lint

I cannot find the configuration for this check, not sure why it's being reported/blocking merges here

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 13, 2025

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/yaml-lint

Details

In response to this:

/override ci/prow/yaml-lint

I cannot find the configuration for this check, not sure why it's being reported/blocking merges here

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.

@JoelSpeed
Copy link
Copy Markdown
Contributor

/override ci/prow/security

I've checked the issue and it's unrelated, I can't clear it in the Snyk dashboard right now for some reason though

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 13, 2025

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/security

Details

In response to this:

/override ci/prow/security

I've checked the issue and it's unrelated, I can't clear it in the Snyk dashboard right now for some reason though

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 13, 2025

@vr4manta: 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-vsphere-ovn-upgrade e117e81 link false /test e2e-vsphere-ovn-upgrade
ci/prow/e2e-azure-operator e117e81 link false /test e2e-azure-operator
ci/prow/e2e-nutanix e117e81 link false /test e2e-nutanix
ci/prow/e2e-vsphere-ovn-serial e117e81 link false /test e2e-vsphere-ovn-serial
ci/prow/e2e-azure-ovn e117e81 link false /test e2e-azure-ovn
ci/prow/e2e-metal-ipi-ovn-ipv6 e117e81 link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/regression-clusterinfra-aws-ipi-mapi e117e81 link false /test regression-clusterinfra-aws-ipi-mapi

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-merge-bot openshift-merge-bot Bot merged commit b3dc35f into openshift:main Mar 13, 2025
@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-api-operator
This PR has been included in build ose-machine-api-operator-container-v4.19.0-202503131541.p0.gb3dc35f.assembly.stream.el9.
All builds following this will include this PR.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants