goroutine panic launching container on xenial

[Adam Stokes]

When deploying upwards of 15 applications using the lxd provider at times at least one agent is stick in an allocating state.

Here is the log from machine 6 in this case is ceph-radosgw, as you can see the underlying lxd container is created and does have an IP and the rest of the applications come up as expected.

http://paste.ubuntu.com/17313966/

Note: interesting bit starts at line 184

Here is the juju status output (tabular, yaml formatted):

http://paste.ubuntu.com/17314052/ (tabular)
http://paste.ubuntu.com/17314074/ (yaml)

This can easily be reproduced by running conjure-up:

sudo apt-add-repository ppa:conjure/next
sudo apt update
sudo apt install conjure-up
conjure-up -d battlemidget/openstack-novalxd

Then during the application walkthrough view select the button that says 'deploy remaining applications with defaults'

[Cheryl Jennings (cherylj)]

There is an upstream fix in godbus. Nate is updating the dependency.

[Cheryl Jennings (cherylj)]

1.25 PR: https://github.com/juju/juju/pull/5363

[Cheryl Jennings (cherylj)]

This panic is present in the machine log:

panic: send on closed channel

goroutine 321 [running]:
panic(0x1cecb00, 0xc8201178b0)
 /usr/lib/go-1.6/src/runtime/panic.go:464 +0x3e6
github.com/godbus/dbus.(*Conn).inWorker(0xc8203b5320)
 /build/juju-core-2avUTs/juju-core-2.0-beta9~20160608~4037~719e6ec/src/github.com/godbus/dbus/conn.go:327 +0x1048
created by github.com/godbus/dbus.(*Conn).Auth
 /build/juju-core-2avUTs/juju-core-2.0-beta9~20160608~4037~719e6ec/src/github.com/godbus/dbus/auth.go:118 +0xf3d