The auto-generated local env does not work in trusty

Bug #1309455 reported by Francesco Banconi on 2014-04-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-quickstart
Critical
Unassigned

Bug Description

Due to bug #1306537 quickstart hangs when trying to bootstrap the initial automatically generated local env, and, more in general, any local environment not specifying "precise" as default series.

While we wait for the bug above to be fixed and the change landed, we can update quickstart in trusty to be smarter, i.e.:

- switch to "trusty" defaults:
  - the suggested default series when creating new environments is "precise" and should be changed to "trusty";
  - we ported the GUI to trusty, so now the GUI can be deployed by default from the trusty charm.

- use the bootstrap node series to select which GUI charm to deploy:
  - if the bootstrap node series is "precise", use the precise charm;
  - otherwise default to trusty;
  - only deploy to a new machine if the local provider is used or the bootstrap node series is not "precise" or "trusty".

- include the "trusty" default-series field in the initial auto-generated local env: this way the initial environment should work even before fixing core bug 1306537.

Related branches

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

Other bug subscribers