Problem with lxd on master - How do I debug this?

[Matthew Williams]

Hey folks,

the lxd provider has been working fine for me - until this morning. I'm
running on master (1cb8f0)

I've attached output from juju debug-log juju status and lxd list, can
someone help me work out what I should do to resolve this.

The history leading up the attached logs is:

1) Everything was working
2) A deployed a charm that had a hook install error (I was debugging said
charm, so that was expected). I couldn't ssh to the unit. I got the
following error:
$ juju ssh foobar/0
ERROR error fetching address for unit "foobar/0": private no address.

juju debug log showed:

 machine-4: 2016-02-01 11:53:39 ERROR juju.worker runner.go:229 exited
"machiner": setting machine addresses: cannot set machine addresses of
machine 4: state changing too quickly; try again soon

After doing what debug I can I destroyed the controller. Now whenever I
bootstrap a lxd environment I get the state server and everything else
get's stuck in allocation. Attached is more detailed stuff from the logs.
What should I do to work out what's going on here?

Matty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160201/ec12229b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lxd-issue.log
Type: text/x-log
Size: 2470 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160201/ec12229b/attachment.bin>