lxc deploys broken on precise

Bug #1350011 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Ian Booth
1.20
Fix Released
Critical
Ian Booth

Bug Description

stable (1.20) and devel (master) are broken by a commit that changes lxc. Only precise is affected. trusty and utopic are fine. I don't believe architecture is a factor

The essential error seen in the logs are
    machine-0: 2014-07-29 18:29:00 ERROR juju.container.lxc lxc.go:244 container failed to start: cannot determine the lxc-start version: exit status 1
    machine-0: 2014-07-29 18:29:00 ERROR juju.provisioner provisioner_task.go:420 cannot start instance for machine "1": cannot determine the lxc-start version: exit status 1

Once this error is experienced, juju doesn't not cleanup. The lxc containers are left stopped with confs in /etc/lxc/auto. The machine must be manually purged.

Related branches

Revision history for this message
Curtis Hovey (sinzui) wrote :
Revision history for this message
Curtis Hovey (sinzui) wrote :

The breaking commits were changes to the packagins deps

1.20 5a5d19485962fbf344731ff1b0896fe96ad540ce Merge pull request #410 from katco-/upstream-1.20
master b76ac1d485abeeb7cb056503282648be8c9b796b Merge pull request #418 from katco-/update-golxc-version

the actual issue is in golxc revno 11

Revision history for this message
Curtis Hovey (sinzui) wrote :

The precise machine
~$ apt-cache policy lxc
lxc:
  Installed: 1.0.0~alpha1-0ubuntu14.1~ubuntu12.04.1~juju1

The trusty machine that passed has
    1.0.4-0ubuntu0.1

Revision history for this message
Curtis Hovey (sinzui) wrote :

See http://juju-ci.vapour.ws:8080/job/local-deploy-precise-amd64/ for specific details
    1.20 http://juju-ci.vapour.ws:8080/job/local-deploy-precise-amd64/1709/console
    master http://juju-ci.vapour.ws:8080/job/local-deploy-precise-amd64/1714/console

Since the first failure will leave broken containers subsequent retests will report the containers already exist. So besides this bug, it is clear juju is leaving a broken system behind.

Changed in juju-core:
assignee: nobody → Katherine Cox-Buday (cox-katherine-e)
status: Triaged → In Progress
Revision history for this message
Katherine Cox-Buday (cox-katherine-e) wrote :

The golxc library attempts to look at the --version flag to intelligently determine what flag to use to specify a console-file. It looks like in this particular version of lxc-start there is no --version flag. We will have to reconsider how to determine what the console-file flag is.

Ian Booth (wallyworld)
Changed in juju-core:
assignee: Katherine Cox-Buday (cox-katherine-e) → Ian Booth (wallyworld)
Ian Booth (wallyworld)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
importance: Critical → High
Curtis Hovey (sinzui)
Changed in juju-core:
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.