Skip to content

AWS e2e provider should identify zone and master and multizone #2507

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

Merged

Conversation

smarterclayton
Copy link
Contributor

Allows certain tests to pass

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 5, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 5, 2019
@smarterclayton smarterclayton added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2019
@openshift-merge-robot openshift-merge-robot merged commit f6ea7aa into openshift:master Jan 5, 2019
@openshift-ci-robot
Copy link
Contributor

@smarterclayton: Updated the following 2 configmaps:

  • prow-job-cluster-launch-installer-e2e configmap using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-src configmap using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml

In response to this:

Allows certain tests to pass

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.

@smarterclayton smarterclayton deleted the configure_aws_e2e branch April 24, 2019 14:01
wking added a commit to wking/openshift-release that referenced this pull request 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.  This sets us up
for sharding GCP by region, if we ever need that (e.g. GCP has an
outage in one region).

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 still wish the end-to-end suite pulled the region out of the cluster
itself, but until it does, lean on the Infrastructure status [1] like
we've been doing for AWS since bf0a271 (AWS e2e provider should
identify zone and master and multizone, 2019-01-05, openshift#2507).

[1]: https://github.com/openshift/api/blob/164a2fb63b5f12918c439a5a0a768aa911bcad99/config/v1/types_infrastructure.go#L327-L328
wking added a commit to wking/ci-tools that referenced this pull request Dec 14, 2020
I still wish the end-to-end suite pulled the region out of the cluster
itself, but until it does, lean on the Infrastructure status [1] like
we've been doing for AWS since openshift/release@bf0a271f5c (AWS e2e
provider should identify zone and master and multizone, 2019-01-05,
openshift/release#2507).  The hard-coding I'm replacing here was fine
until the GCP region became dynamic in 00ebab1
(pkg/steps/clusterinstall/template: Get region from Boskos lease,
2020-12-11, openshift#1527).

[1]: https://github.com/openshift/api/blob/164a2fb63b5f12918c439a5a0a768aa911bcad99/config/v1/types_infrastructure.go#L327-L328
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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants