Addresses for fan-networking sole containers missing public or local-cloud address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
LXDs using solely fan-networking and not using any of the provider networks (for example deployed on Azure or VMWare provider with manual machines) do not list any ip addresses with the key 'public' or 'local-cloud'. Trying to load the data with python-libjuju fails to return any unit IP and returns None:
https:/
Shouldn't there be a 'local-cloud' address corresponding to the fan-networking address in case there isn't any other available IP address for the juju spaces?
In this example a etcd unit was deployed on a kvm on VMWare, the etcd has it's bindings to an available space, but the container-
I understand that changing 'fan' to 'provider' will be a solution to this, but then re-deployment of the lxd containers will have to be done + additional IPs from the provider network, which the customers might not agree to.
python-libjuju related issue: https:/ /github. com/juju/ python- libjuju/ issues/ 611