upgrade from 1.10 to trunk cannot deploy containers
Bug #1199913 reported by
William Reade
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
lp:~jameinel/juju-core/api-connect-upgrade-1199915
- Juju Engineering: Pending requested
-
Diff: 191 lines (+166/-0)4 files modifiedcmd/jujud/machine.go (+4/-0)
cmd/jujud/upgradevalidation.go (+73/-0)
utils/apt.go (+45/-0)
utils/apt_test.go (+44/-0)
Changed in juju-core: | |
milestone: | none → 1.11.2 |
Changed in juju-core: | |
milestone: | 1.11.2 → 1.11.3 |
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.
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)