"juju bootstrap ... lxd" fails if lxd listening to some but not all addresses

Bug #1555475 reported by John A Meinel on 2016-03-10
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju
High
Unassigned

Bug Description

Possibly just a bug in LXD (reported here https://github.com/lxc/lxd/issues/1732)

If you configure LXD to listen on *a* port with LXD init (in my case I had set "localhost:8443"), then Juju tries to configure LXD to listen on all IP addresses on port 8443 (via core.https_address = "[::]:8443")
However, that fails to reconfigure because LXD tries to apply the new configuration, but cannot bind to port 8443 because it is already running on port 8443.

I'm unsure if we should continue bootstrap if reconfiguring the listening ports fails. Because I'd expect Juju is going to fail to work if LXD does not end up configured to listen on port 8443 on the bridge that the containers come up in. (I need more testing to know that for sure).

John A Meinel (jameinel) on 2016-03-10
summary: "juju bootstrap ... lxd" fails if lxd listening to some but not all
- ports
+ addresses
John A Meinel (jameinel) wrote :

It looks like you should be able to do "lxc config unset core.https_address; lxc config set core.https_addresses [::]:8443". The reason it fails is because there is a bug if you use "localhost:8443". If you use "127.0.0.1:8443" then unset && set works correctly.

tags: added: juju-release-support
Curtis Hovey (sinzui) on 2016-03-25
Changed in juju-core:
milestone: 2.0-beta3 → 2.0-beta4
tags: added: 2.0-count
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.1
affects: juju-core → juju
Changed in juju:
milestone: 2.0.1 → none
milestone: none → 2.0.1
Curtis Hovey (sinzui) on 2016-10-28
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints