Add missing GCE regions #6935

Merged
merged 1 commit into from Feb 13, 2017

Conversation

Projects
None yet
6 participants
Contributor

reedobrien commented Feb 7, 2017

Description of change

This PR adds the US West and Asia Northeast regions to GCE.

Why is this change needed?
Because they are newish and missing.

QA steps

  1. run the unit tests. ($juju/cloud & $JUJU/cmd/juju/cloud specifically changed)

How do we verify that the change works?
Get validation from QA

Documentation changes

N/A
Does it affect current user workflow? CLI? API?
No

Bug reference

https://bugs.launchpad.net/juju/+bug/1662449

Contributor

reedobrien commented Feb 7, 2017

!!build!!

Contributor

reedobrien commented Feb 7, 2017

$$merge$$

Contributor

jujubot commented Feb 7, 2017

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

Contributor

jujubot commented Feb 7, 2017

Build failed: Tests failed
build url: http://juju-ci.vapour.ws:8080/job/github-merge-juju/10230

Owner

wallyworld commented Feb 7, 2017

$$merge$$

Contributor

jujubot commented Feb 7, 2017

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

Contributor

jujubot commented Feb 7, 2017

Build failed: Tests failed
build url: http://juju-ci.vapour.ws:8080/job/github-merge-juju/10232

Contributor

reedobrien commented Feb 7, 2017

Waiting for QA tests on the fallback-public-cloud.yaml file to complete. Should be done tomorrow afternoon.

Owner

jameinel commented Feb 9, 2017

Shouldn't it be possible for you to test this just by doing "juju bootstrap gce/$REGION" ? (especially if its using a version string that means it will use a local agent.)

Also, last comment from 2 days ago says that it will be done "tomorrow" which is now "yesterday". :)

Contributor

reedobrien commented Feb 9, 2017

I did. They worked. However, AFAIU QA blocks landing on changes to fallback-public-clouds.yaml as that is what gets signed and uploaded. It turns out there is a problem with aws ap-northeast-2 which is unrelated to this PR, but QA doesn't want to sign and publish an updated public-clouds.yaml due to that issue.

I tried a quick removal of ap-northeast-2 since it is broken, figuring we could fix it and put it back once fixed. That ran into other opposition, however. And so yesterday turned into today...

I am looking at fixing https://bugs.launchpad.net/juju/+bug/166304 currently.

Contributor

abentley commented Feb 9, 2017

Just so you're aware, we consider the ap-northeast-2 bug a problem until there is a juju release (not a beta or rc) that supports ap-northeast-2. As such, I am updating streams.canonical.com to add the GCE regions and remove ap-northeast-2.

Here's the unsigned version I will be using. https://bazaar.launchpad.net/~canonical-juju-qa/+junk/clouds-unsigned/view/15/clouds.yaml

Contributor

abentley commented Feb 9, 2017

BTW @jameinel just bootstrapping is not sufficient. The ap-northeast-2 bug is only evident when we deploy.

Contributor

reedobrien commented Feb 10, 2017

$$merge$$

Contributor

jujubot commented Feb 10, 2017

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

Contributor

jujubot commented Feb 10, 2017

Build failed: Tests failed
build url: http://juju-ci.vapour.ws:8080/job/github-merge-juju/10275

Owner

wallyworld commented Feb 13, 2017

$$merge$$

Contributor

jujubot commented Feb 13, 2017

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

Contributor

jujubot commented Feb 13, 2017

Build failed: Tests failed
build url: http://juju-ci.vapour.ws:8080/job/github-merge-juju/10278

Contributor

abentley commented Feb 13, 2017

$$merge$$

Contributor

jujubot commented Feb 13, 2017

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

@jujubot jujubot merged commit 309a02d into juju:develop Feb 13, 2017

1 check failed

github-check-merge-juju Built PR, ran unit tests, and tested LXD deploy. Use !!.*!! to request another build. IE, !!build!!, !!retry!!
Details

@reedobrien reedobrien deleted the reedobrien:bug/1662449 branch Feb 22, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment