This bug was fixed in the package lxc - 1.1.5-0ubuntu1
---------------
lxc (1.1.5-0ubuntu1) xenial; urgency=medium
* New upstream bugfix release (1.1.5)
(LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619)
* Drop proxy detection from the autopkgtest exercise script.
-- Stéphane Graber <stgra...@ubuntu.com> Mon, 09 Nov 2015 14:22:16
-0500
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1510619
Title:
Wily: add machine fails using kvm and lxcbr0
Status in juju-core:
Invalid
Status in lxc package in Ubuntu:
Fix Released
Bug description:
Juju fails to start a machine after add-machine takes place.
My environments.yaml:
local:
type: local
container: kvm
network-bridge: lxcbr0
Status output:
ubuntu@ancient-spot:~$ juju status
environment: local
machines:
"0":
agent-state: started
agent-version: 1.24.7.1
dns-name: localhost
instance-id: localhost
series: wily
state-server-member-status: has-vote
"1":
agent-state: pending
instance-id: ubuntu-local-machine-1
series: wily
hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
debug log:
http://paste.ubuntu.com/12980615/
I never see anything in the logs which indicate machine-1 is being deployed
or what else could be going on with it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
