precise/ trusty mix up in local provider

[Matthew Williams]

bootstrapped a local provider on precise

juju version: 1.18.1-precise-amd6

juju deploy ubuntu returns the trusty version of the charm giving

environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.18.1.1
    dns-name: localhost
    instance-id: localhost
    series: precise
  "1":
    instance-id: pending
    series: trusty
services:
  ubuntu:
    charm: cs:trusty/ubuntu-0
    exposed: false
    units:
      ubuntu/0:
        agent-state: pending
        machine: "1"

http://paste.ubuntu.com/7259886/

[John A Meinel (jameinel)]

This is by intent. Something like "ubuntu" means "give me the best version
of the Ubuntu workload", and since there is now a Trusty version, that is
what we give you. As long as it is capable of bringing up a Trusty LXC
container (minus the Kernel), which may take a while since Local has to
download the image the first time you request it.

You can always do "juju deploy precise/ubuntu" if you are sure that is what
you want. And if you know that is what you always want you can set
"default-series: precise" for your Local envinronment.

We *could* have local always prefer the same series, but if (for example)
the Wordpress charm on Trusty is much more maintained and reliable, do you
really want to force the Precise version to be installed?

On Wed, Apr 16, 2014 at 5:19 PM, Curtis Hovey <email address hidden> wrote:

> ** Changed in: juju-core
> Status: Confirmed => Triaged
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1308367
>
> Title:
> precise/ trusty mix up in local provider
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1308367/+subscriptions
>

[John A Meinel (jameinel)]

We do intend that we will run the "best" version of a charm based on what the charm store reports to us as the best version of "ubuntu".

We have 2 fixes that address the "it tried and just didn't work", which should allow it to still actually bring up a Trusty instance and get the right tools and install the charm correctly.

We talked about making it so the local provider sets "default-series: LOCALHOST_SERIES" but it actually doesn't seem necessary, and makes local provider less special vs others.

[Tim Penhey (thumper)]

We want to have better documentation about how to get what you wanted (if you want to have only specific series on the local provider then how do you achieve that)

[Nick Veitch (evilnick)]

Can we reimplement the commented out selection of default-series in the
generate-config template? I think that would make it easier to explain in
docs.
On Apr 29, 2014 1:55 PM, "Tim Penhey" <email address hidden> wrote:

> We want to have better documentation about how to get what you wanted
> (if you want to have only specific series on the local provider then how
> do you achieve that)
>
>
> ** Also affects: juju-core/docs
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to docs.
> Matching subscriptions: docs-bugs
> https://bugs.launchpad.net/bugs/1308367
>
> Title:
> precise/ trusty mix up in local provider
>
> Status in juju-core:
> Won't Fix
> Status in juju-core docs series:
> New
>
> Bug description:
> bootstrapped a local provider on precise
>
> juju version: 1.18.1-precise-amd6
>
> juju deploy ubuntu returns the trusty version of the charm giving
>
> environment: local
> machines:
> "0":
> agent-state: started
> agent-version: 1.18.1.1
> dns-name: localhost
> instance-id: localhost
> series: precise
> "1":
> instance-id: pending
> series: trusty
> services:
> ubuntu:
> charm: cs:trusty/ubuntu-0
> exposed: false
> units:
> ubuntu/0:
> agent-state: pending
> machine: "1"
>
> http://paste.ubuntu.com/7259886/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1308367/+subscriptions
>