upgrade from 1.10 to trunk cannot deploy containers

Bug #1199913 reported by William Reade
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Critical
Unassigned

Bug Description

...because the lxc package was not installed by cloudinit before we had containers available. sudo apt-get install lxc fixes this.

Related branches

William Reade (fwereade)
Changed in juju-core:
milestone: none → 1.11.2
Revision history for this message
John A Meinel (jameinel) wrote :

It also spams the log file because it cannot find "lxc-ls".
Which causes that task to return an error, causing the runner to kill off the machiner environ-provider, apiserver upgrader and firewaller.
And then restart them, only to kill them, ad nauseum.

I don't think this is the same bug as https://bugs.launchpad.net/juju-core/+bug/1199915
But it is what I'm seeing right now trying to upgrade juju-core bootstrapped with 1.10 => trunk (using trunk)

Changed in juju-core:
milestone: 1.11.2 → 1.11.3
Revision history for this message
John A Meinel (jameinel) wrote :

To clarify, missing 'lxc-ls' is killing that task, which ends up killing and restarting all tasks. So it isn't just that this spams the log file and cannot deploy containers, it actually breaks the running system after an upgrade until lxc is installed.

Go Bot (go-bot)
Changed in juju-core:
status: Triaged → Fix Committed
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.