juju deploy --to lxc:0 cs:trusty/ubuntu creates precise container

Bug #1302820 reported by David Britton
40
This bug affects 6 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Tim Penhey
1.18
Fix Released
High
Martin Packman

Bug Description

I have a precise bootstrap node, and I run the following to test a trusty charm:

juju deploy --to lxc:0 cs:trusty/ubuntu

And I see the following on the bootstrap host:

 16318 ? S 0:00 \_ lxc-create -n juju-machine-0-lxc-0 -t ubuntu-cloud -f /var/lib/juju/containers/juju-machine-0-lxc-0/lxc.conf -- --debug --userdata /var/lib/juju/containers/juju-machine-0-lxc-0/cloud-init --hostid juju-machine-0-lxc-0 -r precise

Notice the '-r precise'

Indeed, I end up with a precise container, and juju status output that still shows "trusty/ubuntu":

machines:
  "0":
    agent-state: started
    agent-version: 1.17.7
    dns-name: xxx
    instance-id: i-yyyyyy
    instance-state: running
    series: precise
    containers:
      0/lxc/0:
        agent-state: started
        agent-version: 1.17.7
        dns-name: 10.0.3.120
        instance-id: juju-machine-0-lxc-0
        series: trusty
        hardware: arch=amd64
    hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
(...)
  ubuntu:
    charm: cs:trusty/ubuntu-0
    exposed: false
    units:
      ubuntu/0:
        agent-state: started
        agent-version: 1.17.7
        machine: 0/lxc/0
        public-address: 10.0.3.120

Related branches

David Britton (dpb)
description: updated
description: updated
William Reade (fwereade)
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.19.0
Revision history for this message
Tim Penhey (thumper) wrote :

worker/provisioner/lxc-broker.go:69
 series := args.Tools.OneSeries()

The lxc broker is created with the tools of the agent. These same tools are passed down to the container being created.

Yes it appears that the brokers only create series that match the host.

Tim Penhey (thumper)
Changed in juju-core:
assignee: nobody → Tim Penhey (thumper)
status: Triaged → In Progress
Tim Penhey (thumper)
Changed in juju-core:
status: In Progress → Fix Committed
Revision history for this message
James Page (james-page) wrote :

Will this be backported to 1.18 series? sounds important.

Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
Revision history for this message
John A Meinel (jameinel) wrote :

I added a target for 1.18.2, but AFAIK there are no current plans to backport this.

We can if someone pushes for it, though right now I think we're trying to get 1.19 into stable shape and get that instead.

Tycho Andersen (tycho-s)
tags: added: cloud-installer
Revision history for this message
Adam Stokes (adam-stokes) wrote :

We need this backported to 1.18 as it blocks our ability to deploy certain configurations.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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