juju-core

juju 1.18 (local provider) depends on lxc 1.0.0 but nothing forces it to install on precise

Bug #1311909 reported by Christian Reis
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Curtis Hovey
juju-core 1.19.1
1.18
Fix Released
High
Curtis Hovey

Bug Description

I'm on precise, using ppa:juju/stable, and using the local provider. I just upgraded from 1.16 to 1.18 and apart from a few other things that seem to have gone wrong (which I will file bugs for separately once I understand them) one very bad thing is that juju is no longer able to add new machines; every machine added fails with very little in the logs and a simple:

    agent-state-info: '(error: container failed to start)'

in the juju status output.

It turns out the problem is that I am on an old version of lxc, which happens to be the stock version on precise.

root@chorus:/var/lib/lxc/juju-local-machine-32# dpkg -l | grep lxc
ii lxc 0.7.5-3ubuntu69 Linux containers userspace tools

The version in backports (which is similar to the the cloud archive version, both 1.0.0) works.

Christian Reis (kiko)
summary: - juju 1.18 (local provider) 1.0.0 but nothing forces it to install on
- precise
+ juju 1.18 (local provider) depends on lxc 1.0.0 but nothing forces it to
+ install on precise
Curtis Hovey (sinzui)
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
tags: added: packaging upgrade-juju
Changed in juju-core:
milestone: none → 1.20.0
Revision history for this message
Christian Reis (kiko) wrote :

Shouldn't this be fixed in the 1.18 packaging to avoid the problem affecting others?

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

Hi Kiko.

Yes this needs to be fixed in the 1.18 packages. but since the fix has to be a bug fix only, we may only be able to do a partial fix.

There are a few factors we need consider.
1. the package i question is juju-local which you didn't have installed.
2. Juju 1.19.x demands juju-local to be installed when a local env is bootstrapped...but in this case you upgraded.
3. The source of the lxc package for precise is the cloud-archive, which you didn't have either. Though we say Precise must use it, many do not.

So I think a proper fix involves
1. Change juju-local to require a specific version or greater
2. Change upgrade-juju to abort if the host doesn't have juju-local involved
3. copy the lxc package to the juju stable archive as a courtesy.

Curtis Hovey (sinzui)
Changed in juju-core:
assignee: nobody → Curtis Hovey (sinzui)
milestone: 1.20.0 → 1.19.1
Curtis Hovey (sinzui)
Changed in juju-core:
status: Triaged → In Progress
Curtis Hovey (sinzui)
Changed in juju-core:
status: In Progress → Fix Committed
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.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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