public cloud data out of sync

Bug #1769879 reported by Ian Booth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Unassigned

Bug Description

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.

Revision history for this message
Ian Booth (wallyworld) wrote :

Without digging too deeply, it may be that just the public-clouds.yaml needs to be updated and not juju itself. But we should check that 2.3 and 2.4 ship with consistent cloud definitions.

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1769879] [NEW] public cloud data out of sync

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
>

Revision history for this message
Ian Booth (wallyworld) wrote :

We should add a CI test for this. The update-clouds command would suffice rather than a refresh install.

Changed in juju:
milestone: 2.4-beta2 → none
Ian Booth (wallyworld)
Changed in juju:
milestone: none → 2.4-rc1
Revision history for this message
Christopher Lee (veebers) wrote :

I've updated the published public-clouds so that it's up to date (includes eu-west-3 etc.)

Ian Booth (wallyworld)
no longer affects: juju/2.3
Changed in juju:
status: Triaged → Fix Committed
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Marking as Fix Released as 2.4.0 is out.

Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.