Skip to content

Conversation

@jstuever
Copy link
Contributor

Before this change, the GCP UPI workflow hard coded the zones in the
bootstrap and control-plane templates. It assumed every region had zones
$REGION-{a,b,c}. However, in some regions this is not the case.

This change adds the zone(s) as parameters to the templates and updates
the docs accordingly. The list of zones is now fetched from gcp, and
then used to populate the templates.

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 24, 2019
Copy link
Member

Choose a reason for hiding this comment

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

Do all regions have 3+ zones?

Copy link
Contributor Author

@jstuever jstuever Sep 24, 2019

Choose a reason for hiding this comment

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

They appear to, yes. However, this is ultimately a mapping of zones to masters... the zones could be used more than once if a case is found where this is not true.

Before this change, the GCP UPI workflow hard coded the zones in the
bootstrap and control-plane templates. It assumed every region had zones
$REGION-{a,b,c}. However, in some regions this is not the case.

This change adds the zone(s) as parameters to the templates and updates
the docs accordingly. The list of zones is now fetched from gcp, and
then used to populate the templates.
@jstuever
Copy link
Contributor Author

/retest

@wking
Copy link
Member

wking commented Sep 25, 2019

/ltgm

Although I expect we'll keep failing the unrelated CI jobs until origin gets sorted post-rebase.

@jstuever
Copy link
Contributor Author

/retest

@jstuever
Copy link
Contributor Author

@wking s/ltgm/lgtm/

@abhinavdahiya
Copy link
Contributor

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Sep 25, 2019
@abhinavdahiya
Copy link
Contributor

/test e2e-aws-upgrade

@wking
Copy link
Member

wking commented Sep 26, 2019

Dunno what this is:

error: could not run steps: step src failed: could not wait for build: the build src failed after 1m5s with reason PushImageToRegistryFailed: Failed to push the image to the registry.

/retest

@wking
Copy link
Member

wking commented Sep 26, 2019

LB timeout.

/retest

@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 72315be into openshift:master Sep 26, 2019
@jstuever jstuever deleted the cors1240 branch September 26, 2019 16:31
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/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants