Juju fails to bootstrap lxd-test localhost controller

[Udi Nachmany]

Juju 2.0-rc3, when trying to follow https://jujucharms.com/docs/stable/getting-started with the command
$ juju bootstrap lxd-test localhost

I get the errors in the attached file.
Note that the solution in bug https://bugs.launchpad.net/juju/+bug/1619971 is no help.

[Tycho Andersen (tycho-s)]

There are two bugs here, and I believe #1619971 is a bug in LXD's client API. The other bug is that juju somehow couldn't talk to LXD over the bridge, although other containers on the network could.

[John A Meinel (jameinel)]

not being able to bootstrap would obviously be a big issue. I don't fully understand what is actually failing here. Looking at the tail end of the log file:
2016-10-12 15:18:52 INFO juju.cmd supercommand.go:63 running jujud [2.0-rc3 gc go1.6.2]
2016-10-12 15:19:02 ERROR cmd supercommand.go:458 new environ: creating LXD client: Get https://10.189.178.1:8443/1.0: Unable to connect to: 10.189.178.1:8443
ERROR failed to bootstrap model: subprocess encountered error code 1
udi@udi-MacBookPro:~$ juju list-controllers

Seems to say that it was trying to set up the jujud agent inside the container, and that agent failed to contact the host's LXD agent. (Unable to connect to 10.189.178.1:8443)

I certainly bootstrap 'lxd' fairly often and have never seen this. Juju itself should be ensuring that the LXD agent is running and configured to listen on all interfaces.

Can you give the output of
  lxc config show
I would expect to see something about:
  core.https_address:

Tycho mentions (if I'm understanding him correctly) that maybe there was a bug in LXD that was preventing it from listening to the address on the bridge?

Are you able to reproduce this failure? I haven't been able to, so it would be good to know if there is something specific to your configuration.

You can also do things like "juju bootstrap --debug" which will be much more verbose about what we're doing and might give more of a clue what is going wrong.

[John A Meinel (jameinel)]

could this be the "disabled IPv6" support failing?
I wonder if this is actually just bug #1633362

[Udi Nachmany (udi-nachmany)]

Sorry--will do tomorrow!

On Sun, 5 Feb 2017 at 13:15 John A Meinel <email address hidden> wrote:

> could this be the "disabled IPv6" support failing?
> I wonder if this is actually just bug #1633362
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1632757
>
> Title:
> Juju fails to bootstrap lxd-test localhost controller
>
> Status in juju:
> Incomplete
>
> Bug description:
> Juju 2.0-rc3, when trying to follow
> https://jujucharms.com/docs/stable/getting-started with the command
> $ juju bootstrap lxd-test localhost
>
> I get the errors in the attached file.
> Note that the solution in bug
> https://bugs.launchpad.net/juju/+bug/1619971 is no help.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1632757/+subscriptions
>
--
*Canonical* | Head of Certified Public Cloud | <email address hidden> |
M. [phone] | T. [phone] ext. 2447
*Ubuntu* - *The platform of scale-out computing* | Discover more - Twitter
<https://twitter.com/ubuntucloud> Web <http://www.ubuntu.com/cloud> Blog
<http://insights.ubuntu.com/products-and-services/cloud/>

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]