Comment 2 for bug 1769879

I believe what happened is that I rebuilt the cloud definition for aws (and
it seems someone did for google), but we somehow didn't update the
public-clouds.yaml official definition. I'm guessing we just need to
publish the complete list, rather than change juju itself.

On Tue, May 8, 2018 at 4:36 PM, Ian Booth <email address hidden> wrote:

> Public bug reported:
>
> On a fresh juju 2.4 install, running the first command syncs public
> cloud data. This is the result:
>
> deleted cloud region:
> - aws/eu-west-3
> - google/europe-west2
> - google/europe-west3
> - google/southamerica-east1
> - google/us-east4
>
> There's a mismatch between what we ship and what's in public-
> clouds.yaml. This needs to be fixed before release, and 2.3 also needs
> to be checked.
>
> ** Affects: juju
> Importance: Critical
> Status: Triaged
>
> ** Affects: juju/2.3
> Importance: High
> Status: Triaged
>
> ** Also affects: juju/2.3
> Importance: Undecided
> Status: New
>
> ** Changed in: juju/2.3
> Milestone: None => 2.3.8
>
> ** Changed in: juju/2.3
> Importance: Undecided => High
>
> ** Changed in: juju/2.3
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1769879
>
> Title:
> public cloud data out of sync
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1769879/+subscriptions
>