Skip to content

Conversation

@patrickdillon
Copy link
Contributor

@patrickdillon patrickdillon commented Mar 11, 2020

Adds vSphere IPI e2e tests. Depends on openshift/installer#3327.
Also related is #7560. This could be merged first and #7560 updated.

  • pre steps:
    • reserve IPS
    • set up DNS records in route53
    • write install-config
  • install/test:
    • install using upi image in order to include CA cert
  • test
  • teardown
    • cluster teardown
    • release vips
    • delete DNS records

Updates installer presubmit job

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 11, 2020
@patrickdillon patrickdillon force-pushed the vsphere-ipi-steps branch 5 times, most recently from 35441f6 to 0ac8acf Compare March 12, 2020 20:23
@openshift-ci-robot openshift-ci-robot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Mar 12, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Mar 12, 2020
@patrickdillon patrickdillon force-pushed the vsphere-ipi-steps branch 5 times, most recently from 30d71aa to ee10718 Compare March 13, 2020 14:48
@patrickdillon
Copy link
Contributor Author

/test pj-rehearse

@patrickdillon patrickdillon force-pushed the vsphere-ipi-steps branch 3 times, most recently from 5c6d1ec to e0fa706 Compare March 13, 2020 19:32
@patrickdillon
Copy link
Contributor Author

/test pj-rehearse

@patrickdillon patrickdillon force-pushed the vsphere-ipi-steps branch 7 times, most recently from 19f52bd to 4a71175 Compare March 17, 2020 18:56
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 17, 2020
Copy link
Member

Choose a reason for hiding this comment

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

I'd rather extract this from a mounted secret (/var/run/secrets/...), instead of hard-coding it in two separate steps.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

What about a BASE_DOMAIN envvar set in the job?

Copy link
Contributor

Choose a reason for hiding this comment

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

should be move towards openshift/installer#3292 ?

@patrickdillon patrickdillon force-pushed the vsphere-ipi-steps branch 6 times, most recently from 9579306 to aaecbc2 Compare March 24, 2020 02:30
@patrickdillon
Copy link
Contributor Author

/test pj-rehearse

@patrickdillon patrickdillon force-pushed the vsphere-ipi-steps branch 3 times, most recently from 83d17b9 to 33e99dc Compare March 25, 2020 00:52
- pre steps:
  reserve IPS
  set up DNS records in route53
  write install-config
- install/test:
  install using upi image in order to include CA cert
  test
- teardown
  cluster teardown
  release vips
  delete DNS records
Note that this job is currently named e2e-vsphere-steps. The intention is to name it e2e-vsphere, which is currently the name of the upi job. Renaming this job and the upi job will be handled in a separate commit.
@openshift-ci-robot
Copy link
Contributor

@patrickdillon: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift/installer/master/vsphere-steps 7a9790f917175d702048b31da983a8e2f20ff184 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-vsphere-steps 9883317 link /test pj-rehearse
ci/prow/pj-rehearse 9883317 link /test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 25, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, patrickdillon

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 25, 2020
@openshift-merge-robot openshift-merge-robot merged commit 560ed51 into openshift:master Mar 25, 2020
@openshift-ci-robot
Copy link
Contributor

@patrickdillon: Updated the following 9 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster default using the following files:
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.yaml
  • job-config-master configmap in namespace ci at cluster default using the following files:
    • key openshift-installer-master-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-master-presubmits.yaml
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/OWNERS
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/dns/OWNERS
    • key ipi-conf-vsphere-dns-commands.sh using file ci-operator/step-registry/ipi/conf/vsphere/dns/ipi-conf-vsphere-dns-commands.sh
    • key ipi-conf-vsphere-dns-ref.yaml using file ci-operator/step-registry/ipi/conf/vsphere/dns/ipi-conf-vsphere-dns-ref.yaml
    • key ipi-conf-vsphere-chain.yaml using file ci-operator/step-registry/ipi/conf/vsphere/ipi-conf-vsphere-chain.yaml
    • key ipi-conf-vsphere-commands.sh using file ci-operator/step-registry/ipi/conf/vsphere/ipi-conf-vsphere-commands.sh
    • key ipi-conf-vsphere-ref.yaml using file ci-operator/step-registry/ipi/conf/vsphere/ipi-conf-vsphere-ref.yaml
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/vips/OWNERS
    • key ipi-conf-vsphere-vips-commands.sh using file ci-operator/step-registry/ipi/conf/vsphere/vips/ipi-conf-vsphere-vips-commands.sh
    • key ipi-conf-vsphere-vips-ref.yaml using file ci-operator/step-registry/ipi/conf/vsphere/vips/ipi-conf-vsphere-vips-ref.yaml
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/vsphere/OWNERS
    • key ipi-deprovision-vsphere-chain.yaml using file ci-operator/step-registry/ipi/deprovision/vsphere/ipi-deprovision-vsphere-chain.yaml
    • key ipi-deprovision-vsphere-commands.sh using file ci-operator/step-registry/ipi/deprovision/vsphere/ipi-deprovision-vsphere-commands.sh
    • key ipi-deprovision-vsphere-ref.yaml using file ci-operator/step-registry/ipi/deprovision/vsphere/ipi-deprovision-vsphere-ref.yaml
    • key ipi-install-install-commands.sh using file ci-operator/step-registry/ipi/install/install/ipi-install-install-commands.sh
    • key OWNERS using file ci-operator/step-registry/ipi/install/vsphere/OWNERS
    • key ipi-install-vsphere-chain.yaml using file ci-operator/step-registry/ipi/install/vsphere/ipi-install-vsphere-chain.yaml
    • key ipi-install-vsphere-commands.sh using file ci-operator/step-registry/ipi/install/vsphere/ipi-install-vsphere-commands.sh
    • key ipi-install-vsphere-ref.yaml using file ci-operator/step-registry/ipi/install/vsphere/ipi-install-vsphere-ref.yaml
    • key OWNERS using file ci-operator/step-registry/origin/e2e/vsphere/OWNERS
    • key origin-e2e-vsphere-workflow.yaml using file ci-operator/step-registry/origin/e2e/vsphere/origin-e2e-vsphere-workflow.yaml
  • job-config-master configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-master-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-master-presubmits.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.yaml
  • ci-operator-master-configs configmap in namespace ci-stg at cluster default using the following files:
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.yaml
  • ci-operator-master-configs configmap in namespace ci-stg at cluster app.ci using the following files:
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.yaml
  • step-registry configmap in namespace ci at cluster default using the following files:
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/OWNERS
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/dns/OWNERS
    • key ipi-conf-vsphere-dns-commands.sh using file ci-operator/step-registry/ipi/conf/vsphere/dns/ipi-conf-vsphere-dns-commands.sh
    • key ipi-conf-vsphere-dns-ref.yaml using file ci-operator/step-registry/ipi/conf/vsphere/dns/ipi-conf-vsphere-dns-ref.yaml
    • key ipi-conf-vsphere-chain.yaml using file ci-operator/step-registry/ipi/conf/vsphere/ipi-conf-vsphere-chain.yaml
    • key ipi-conf-vsphere-commands.sh using file ci-operator/step-registry/ipi/conf/vsphere/ipi-conf-vsphere-commands.sh
    • key ipi-conf-vsphere-ref.yaml using file ci-operator/step-registry/ipi/conf/vsphere/ipi-conf-vsphere-ref.yaml
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/vips/OWNERS
    • key ipi-conf-vsphere-vips-commands.sh using file ci-operator/step-registry/ipi/conf/vsphere/vips/ipi-conf-vsphere-vips-commands.sh
    • key ipi-conf-vsphere-vips-ref.yaml using file ci-operator/step-registry/ipi/conf/vsphere/vips/ipi-conf-vsphere-vips-ref.yaml
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/vsphere/OWNERS
    • key ipi-deprovision-vsphere-chain.yaml using file ci-operator/step-registry/ipi/deprovision/vsphere/ipi-deprovision-vsphere-chain.yaml
    • key ipi-deprovision-vsphere-commands.sh using file ci-operator/step-registry/ipi/deprovision/vsphere/ipi-deprovision-vsphere-commands.sh
    • key ipi-deprovision-vsphere-ref.yaml using file ci-operator/step-registry/ipi/deprovision/vsphere/ipi-deprovision-vsphere-ref.yaml
    • key ipi-install-install-commands.sh using file ci-operator/step-registry/ipi/install/install/ipi-install-install-commands.sh
    • key OWNERS using file ci-operator/step-registry/ipi/install/vsphere/OWNERS
    • key ipi-install-vsphere-chain.yaml using file ci-operator/step-registry/ipi/install/vsphere/ipi-install-vsphere-chain.yaml
    • key ipi-install-vsphere-commands.sh using file ci-operator/step-registry/ipi/install/vsphere/ipi-install-vsphere-commands.sh
    • key ipi-install-vsphere-ref.yaml using file ci-operator/step-registry/ipi/install/vsphere/ipi-install-vsphere-ref.yaml
    • key OWNERS using file ci-operator/step-registry/origin/e2e/vsphere/OWNERS
    • key origin-e2e-vsphere-workflow.yaml using file ci-operator/step-registry/origin/e2e/vsphere/origin-e2e-vsphere-workflow.yaml
Details

In response to this:

Adds vSphere IPI e2e tests. Depends on openshift/installer#3327.
Also related is #7560. This could be merged first and #7560 updated.

  • pre steps:
  • reserve IPS
  • set up DNS records in route53
  • write install-config
  • install/test:
  • install using upi image in order to include CA cert
  • test
  • teardown
  • cluster teardown
  • release vips
  • delete DNS records

Updates installer presubmit job

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.

wking added a commit to wking/openshift-release that referenced this pull request Mar 5, 2021
The ref was born in fa871a1 (Add VSphere IPI e2e steps, 2020-03-23, openshift#7586)
so it could use the upi-installer image to work with a self-signed
certificate.  But vSphere installation hasn't required that since
fe3ea6a (vSphere: remove the use of upi-installer image; which will
prepare for upgrade testing, 2020-10-12, openshift#12725).  Remove the
vSphere-specific step and point consumers at the generic step instead.

Same for the deprovision step.
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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants