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

ci-operator/step-registry/ipi/conf/aws: Get region from Boskos lease #14322

Merged

Conversation

wking
Copy link
Member

@wking wking commented Dec 14, 2020

Like 7aa198b (#12584), but for AWS.

I'm keeping a switch for AWS to give folks a pattern for selecting zones, if AWS breaks a zone in a particular region. We should probably distribute that (and the shared subnets, for shared-subnet tests?) via leases as well, but baby steps.

I'm leaving ci-operator/templates alone; hopefully those will be gone soon. I've already updated ci-tools with openshift/ci-tools@00ebab17e1 (openshift/ci-tools#1527).

I'm also normalizing to uppercase shell variables, now that we are no longer constrained by Go template expansion. Hmm, at least that's why I thought the variables used to be lowercase, see 43e08e7 (#5151). But looking at the templates when de3de20 (#6708), I'm now not sure why these step commands were using lowercase variable names.

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 14, 2020
Like 7aa198b (ci-operator/step-registry/ipi/conf/azure: Get region
from Boskos lease, 2020-10-14, openshift#12584), but for AWS.

I'm keeping a switch for AWS to give folks a pattern for selecting
zones, if AWS breaks a zone in a particular region.  We should
probably distribute that (and the shared subnets, for shared-subnet
tests?) via leases as well, but baby steps.

I'm leaving ci-operator/templates alone; hopefully those will be gone
soon.  I've already updated ci-tools with
openshift/ci-tools@00ebab17e1 (pkg/steps/clusterinstall/template: Get
region from Boskos lease, 2020-12-11, openshift/ci-tools#1527).

I'm also normalizing to uppercase shell variables, now that we are no
longer constrained by Go template expansion.  Hmm, at least that's why
I thought the variables used to be lowercase, see 43e08e7
(ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e:
Push AWS-specific default base domain down into the template,
2019-09-23, openshift#5151).  But looking at the templates when de3de20
(step-registry: add configure and install IPI steps, 2020-01-14, openshift#6708),
I'm now not sure why these step commands were using lowercase
variable names.
@wking wking force-pushed the aws-region-from-boskos-lease branch from 3be357f to 98857c4 Compare December 15, 2020 22:28
@wking
Copy link
Member Author

wking commented Dec 15, 2020

Rebased around #14350 with 3be357f5f8 -> 98857c4.

@jcantrill
Copy link
Contributor

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, wking

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-merge-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/rehearse/openshift/cluster-network-operator/master/e2e-aws-ovn-windows 3be357f5f802c54c7d7c6023d9eed91ed0fcecd0 link /test pj-rehearse
ci/rehearse/kubevirt/hyperconverged-cluster-operator/release-1.2/hco-e2e-image-index-aws 3be357f5f802c54c7d7c6023d9eed91ed0fcecd0 link /test pj-rehearse
ci/rehearse/openshift/cincinnati/master/e2e 3be357f5f802c54c7d7c6023d9eed91ed0fcecd0 link /test pj-rehearse
ci/rehearse/openshift/kubernetes/master/e2e-aws-selfupgrade 3be357f5f802c54c7d7c6023d9eed91ed0fcecd0 link /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/master/functional 98857c4 link /test pj-rehearse
ci/rehearse/openshift/insights-operator/release-4.2/insights-operator-e2e-tests 98857c4 link /test pj-rehearse
ci/rehearse/ComplianceAsCode/content/master/e2e-aws-rhcos4-e8 98857c4 link /test pj-rehearse
ci/rehearse/openshift/cluster-kube-apiserver-operator/master/e2e-aws-serial 98857c4 link /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/master/e2e-operator 98857c4 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-aws-ovn-windows-custom-vxlan 98857c4 link /test pj-rehearse
ci/rehearse/openshift/cluster-samples-operator/master/e2e-aws-jenkins 98857c4 link /test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-aws-proxy 98857c4 link /test pj-rehearse
ci/rehearse/ComplianceAsCode/content/master/e2e-aws-ocp4-cis-node 98857c4 link /test pj-rehearse
ci/rehearse/openshift-knative/serverless-operator/master/4.6-upstream-e2e-aws-ocp-46 98857c4 link /test pj-rehearse
ci/rehearse/openshift/oc/release-4.2/e2e-cmd 98857c4 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-aws-sdn-multi 98857c4 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-proxy 98857c4 link /test pj-rehearse
ci/rehearse/kubevirt/hyperconverged-cluster-operator/master/hco-e2e-image-index-aws 98857c4 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-ovn-hybrid-step-registry 98857c4 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-ovn-ipsec-step-registry 98857c4 link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/master/e2e-upgrade 98857c4 link /test pj-rehearse
ci/prow/pj-rehearse 98857c4 link /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.

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit d98221c into openshift:master Dec 16, 2020
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the following 2 configmaps:

  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key ipi-conf-aws-commands.sh using file ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-commands.sh
  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key ipi-conf-aws-commands.sh using file ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-commands.sh

In response to this:

Like 7aa198b (#12584), but for AWS.

I'm keeping a switch for AWS to give folks a pattern for selecting zones, if AWS breaks a zone in a particular region. We should probably distribute that (and the shared subnets, for shared-subnet tests?) via leases as well, but baby steps.

I'm leaving ci-operator/templates alone; hopefully those will be gone soon. I've already updated ci-tools with openshift/ci-tools@00ebab17e1 (openshift/ci-tools#1527).

I'm also normalizing to uppercase shell variables, now that we are no longer constrained by Go template expansion. Hmm, at least that's why I thought the variables used to be lowercase, see 43e08e7 (#5151). But looking at the templates when de3de20 (#6708), I'm now not sure why these step commands were using lowercase variable names.

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 wking deleted the aws-region-from-boskos-lease branch December 16, 2020 05:34
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
Development

Successfully merging this pull request may close these issues.

5 participants