Skip to content
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.

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

WINC-607: [upi-vsphere] Add support for Windows VM in platform=none workflow #24911

Merged
merged 3 commits into from Feb 11, 2022

Conversation

jrvaldes
Copy link
Contributor

@jrvaldes jrvaldes commented Jan 3, 2022

  • Adds a step to check Windows golden image template in vCenter
  • Adds a step to create a Windows VM in vCenter
  • Adds a step to destroy a Windows VM in vCenter
  • Adds a UPI workflow with pre- and post- chains to provision and deprovision Windows VMs in vSphere
  • Updates WMCO's platform-none-vsphere-e2e-operator test configuration to include a Windows VM (BYOH use case).

Follow-up to #22371

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 3, 2022

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 openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 3, 2022
@jrvaldes
Copy link
Contributor Author

jrvaldes commented Jan 3, 2022

/test pj-rehearse

@jrvaldes
Copy link
Contributor Author

jrvaldes commented Jan 3, 2022

/test pj-rehearse

@jrvaldes
Copy link
Contributor Author

jrvaldes commented Jan 4, 2022

/cc @openshift/openshift-team-windows-containers

@jrvaldes
Copy link
Contributor Author

jrvaldes commented Jan 7, 2022

/test pj-rehearse

@jrvaldes
Copy link
Contributor Author

jrvaldes commented Jan 7, 2022

/test yamllint

@jrvaldes jrvaldes marked this pull request as ready for review January 7, 2022 06:11
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 7, 2022
@jrvaldes jrvaldes marked this pull request as draft January 7, 2022 13:46
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 7, 2022
@jrvaldes
Copy link
Contributor Author

jrvaldes commented Jan 7, 2022

/hold
Depends on openshift/windows-machine-config-operator#858

@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 Jan 7, 2022
@jrvaldes
Copy link
Contributor Author

jrvaldes commented Jan 7, 2022

/test pj-rehearse

@jrvaldes
Copy link
Contributor Author

/test pj-rehearse

@jrvaldes jrvaldes force-pushed the winc-607 branch 2 times, most recently from 4846057 to 34bf45f Compare January 15, 2022 22:34
@jrvaldes jrvaldes changed the title WINC-607: [upi-vsphere] Add support for Windows VM in platform:none workflow WINC-607: [upi-vsphere] Add support for Windows VM in platform=none workflow Jan 15, 2022
@jrvaldes jrvaldes force-pushed the winc-607 branch 3 times, most recently from b28f988 to 9035829 Compare January 18, 2022 04:47
@jrvaldes
Copy link
Contributor Author

/test pj-rehearse

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2022

@jrvaldes: 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/rehearse/openshift/windows-machine-config-operator/release-4.10/platform-none-vsphere-e2e-operator 124e8fd link unknown /test pj-rehearse
ci/rehearse/openshift/windows-machine-config-operator/release-4.9/platform-none-vsphere-e2e-operator 124e8fd link unknown /test pj-rehearse
ci/rehearse/openshift/vmware-vsphere-csi-driver/release-4.9/e2e-vsphere 124e8fd link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.6-e2e-vsphere-upi 6ce5dffded8929936c5981350c6b7920f2bccc9f link unknown /test pj-rehearse
ci/rehearse/openshift/windows-machine-config-operator/release-4.11/platform-none-vsphere-e2e-operator 124e8fd link unknown /test pj-rehearse
ci/prow/pj-rehearse 124e8fd link false /test pj-rehearse
ci/rehearse/openshift/windows-machine-config-operator/release-4.8/platform-none-vsphere-e2e-operator 124e8fd link unknown /test pj-rehearse
ci/rehearse/openshift/windows-machine-config-operator/master/aws-e2e-upgrade 6ce5dffded8929936c5981350c6b7920f2bccc9f link unknown /test pj-rehearse
ci/rehearse/openshift/windows-machine-config-operator/master/platform-none-vsphere-e2e-operator 124e8fd link unknown /test pj-rehearse

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/test-infra repository. I understand the commands that are listed here.

Copy link

@selansen selansen left a comment

Choose a reason for hiding this comment

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

/lgtm

@sebsoto
Copy link
Contributor

sebsoto commented Feb 10, 2022

/hold

@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 Feb 10, 2022
@sebsoto
Copy link
Contributor

sebsoto commented Feb 10, 2022

/approve

@sebsoto
Copy link
Contributor

sebsoto commented Feb 10, 2022

Held to ensure everyone is okay with this

@selansen
Copy link

/lgtm

Copy link
Contributor

@aravindhp aravindhp left a comment

Choose a reason for hiding this comment

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

@jrvaldes the platform:none tests should be added to branches only where we support platform:none and not to all branches like 4.8, 4.9.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2022
@jrvaldes
Copy link
Contributor Author

@jrvaldes the platform:none tests should be added to branches only where we support platform:none and not to all branches like 4.8, 4.9.

From Cluster and OS Pre-Requisites Platform none (BYOH) support starts at 4.8+.

platform:none tests for 4.8 and 4.9 were added in this PR#22371

cc @mansikulkarni96

@aravindhp
Copy link
Contributor

@jrvaldes the platform:none tests should be added to branches only where we support platform:none and not to all branches like 4.8, 4.9.

From Cluster and OS Pre-Requisites Platform none (BYOH) support starts at 4.8+.

platform:none tests for 4.8 and 4.9 were added in this PR#22371

cc @mansikulkarni96

I might be mixing releases up. If we are sure that platform:none is supported in 4.8 then it is fine. Sorry for the noise.

@jrvaldes
Copy link
Contributor Author

@sebsoto
Copy link
Contributor

sebsoto commented Feb 10, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2022
@jrvaldes
Copy link
Contributor Author

/assign @patrickdillon

@rvanderp3
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jrvaldes, mansikulkarni96, rvanderp3, saifshaikh48, sebsoto, selansen

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 Feb 11, 2022
@jrvaldes
Copy link
Contributor Author

/hold cancel

@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 Feb 11, 2022
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 78da9e2 into openshift:master Feb 11, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2022

@jrvaldes: Updated the following 11 configmaps:

  • ci-operator-4.9-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-release-4.9.yaml using file ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-4.9.yaml
  • job-config-4.10 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-release-4.10-presubmits.yaml using file ci-operator/jobs/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-4.10-presubmits.yaml
  • job-config-4.9 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-release-4.9-presubmits.yaml using file ci-operator/jobs/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-4.9-presubmits.yaml
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key OWNERS using file ci-operator/step-registry/upi/conf/vsphere/ova/windows/OWNERS
    • key upi-conf-vsphere-ova-windows-commands.sh using file ci-operator/step-registry/upi/conf/vsphere/ova/windows/upi-conf-vsphere-ova-windows-commands.sh
    • key upi-conf-vsphere-ova-windows-ref.metadata.json using file ci-operator/step-registry/upi/conf/vsphere/ova/windows/upi-conf-vsphere-ova-windows-ref.metadata.json
    • key upi-conf-vsphere-ova-windows-ref.yaml using file ci-operator/step-registry/upi/conf/vsphere/ova/windows/upi-conf-vsphere-ova-windows-ref.yaml
    • key upi-conf-vsphere-commands.sh using file ci-operator/step-registry/upi/conf/vsphere/upi-conf-vsphere-commands.sh
    • key OWNERS using file ci-operator/step-registry/upi/vsphere/windows/OWNERS
    • key OWNERS using file ci-operator/step-registry/upi/vsphere/windows/post/OWNERS
    • key upi-vsphere-windows-post-chain.metadata.json using file ci-operator/step-registry/upi/vsphere/windows/post/upi-vsphere-windows-post-chain.metadata.json
    • key upi-vsphere-windows-post-chain.yaml using file ci-operator/step-registry/upi/vsphere/windows/post/upi-vsphere-windows-post-chain.yaml
    • key upi-vsphere-windows-post-commands.sh using file ci-operator/step-registry/upi/vsphere/windows/post/upi-vsphere-windows-post-commands.sh
    • key upi-vsphere-windows-post-ref.metadata.json using file ci-operator/step-registry/upi/vsphere/windows/post/upi-vsphere-windows-post-ref.metadata.json
    • key upi-vsphere-windows-post-ref.yaml using file ci-operator/step-registry/upi/vsphere/windows/post/upi-vsphere-windows-post-ref.yaml
    • key OWNERS using file ci-operator/step-registry/upi/vsphere/windows/pre/OWNERS
    • key upi-vsphere-windows-pre-chain.metadata.json using file ci-operator/step-registry/upi/vsphere/windows/pre/upi-vsphere-windows-pre-chain.metadata.json
    • key upi-vsphere-windows-pre-chain.yaml using file ci-operator/step-registry/upi/vsphere/windows/pre/upi-vsphere-windows-pre-chain.yaml
    • key upi-vsphere-windows-pre-commands.sh using file ci-operator/step-registry/upi/vsphere/windows/pre/upi-vsphere-windows-pre-commands.sh
    • key upi-vsphere-windows-pre-ref.metadata.json using file ci-operator/step-registry/upi/vsphere/windows/pre/upi-vsphere-windows-pre-ref.metadata.json
    • key upi-vsphere-windows-pre-ref.yaml using file ci-operator/step-registry/upi/vsphere/windows/pre/upi-vsphere-windows-pre-ref.yaml
    • key upi-vsphere-windows-workflow.metadata.json using file ci-operator/step-registry/upi/vsphere/windows/upi-vsphere-windows-workflow.metadata.json
    • key upi-vsphere-windows-workflow.yaml using file ci-operator/step-registry/upi/vsphere/windows/upi-vsphere-windows-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/windows/e2e/operator/test/byoh/OWNERS
    • key windows-e2e-operator-test-byoh-commands.sh using file ci-operator/step-registry/windows/e2e/operator/test/byoh/windows-e2e-operator-test-byoh-commands.sh
    • key windows-e2e-operator-test-byoh-ref.metadata.json using file ci-operator/step-registry/windows/e2e/operator/test/byoh/windows-e2e-operator-test-byoh-ref.metadata.json
    • key windows-e2e-operator-test-byoh-ref.yaml using file ci-operator/step-registry/windows/e2e/operator/test/byoh/windows-e2e-operator-test-byoh-ref.yaml
    • key OWNERS using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/OWNERS
    • key OWNERS using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/post/OWNERS
    • key windows-e2e-operator-test-platform-none-vsphere-post-chain.metadata.json using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/post/windows-e2e-operator-test-platform-none-vsphere-post-chain.metadata.json
    • key windows-e2e-operator-test-platform-none-vsphere-post-chain.yaml using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/post/windows-e2e-operator-test-platform-none-vsphere-post-chain.yaml
    • key OWNERS using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/pre/OWNERS
    • key windows-e2e-operator-test-platform-none-vsphere-pre-chain.metadata.json using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/pre/windows-e2e-operator-test-platform-none-vsphere-pre-chain.metadata.json
    • key windows-e2e-operator-test-platform-none-vsphere-pre-chain.yaml using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/pre/windows-e2e-operator-test-platform-none-vsphere-pre-chain.yaml
    • key windows-e2e-operator-test-platform-none-vsphere-workflow.metadata.json using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/windows-e2e-operator-test-platform-none-vsphere-workflow.metadata.json
    • key windows-e2e-operator-test-platform-none-vsphere-workflow.yaml using file ci-operator/step-registry/windows/e2e/operator/test/platform-none-vsphere/windows-e2e-operator-test-platform-none-vsphere-workflow.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-master.yaml using file ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master.yaml
  • ci-operator-4.10-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-release-4.10.yaml using file ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-4.10.yaml
  • ci-operator-4.11-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-release-4.11.yaml using file ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-4.11.yaml
  • ci-operator-4.8-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-release-4.8.yaml using file ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-4.8.yaml
  • job-config-master-presubmits configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master-presubmits.yaml
  • job-config-4.11 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-release-4.11-presubmits.yaml using file ci-operator/jobs/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-4.11-presubmits.yaml
  • job-config-4.8 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-windows-machine-config-operator-release-4.8-presubmits.yaml using file ci-operator/jobs/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-4.8-presubmits.yaml

In response to this:

  • Adds a step to check Windows golden image template in vCenter
  • Adds a step to create a Windows VM in vCenter
  • Adds a step to destroy a Windows VM in vCenter
  • Adds a UPI workflow with pre- and post- chains to provision and deprovision Windows VMs in vSphere
  • Updates WMCO's platform-none-vsphere-e2e-operator test configuration to include a Windows VM (BYOH use case).

Follow-up to #22371

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/test-infra repository.

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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
10 participants