Addresses for fan-networking sole containers missing public or local-cloud address

Bug #1956356 reported by Diko Parvanov
6
This bug affects 1 person
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://github.com/juju/python-libjuju/blob/master/juju/machine.py#L240

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-networking-method is set to fan.

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.

Revision history for this message
Diko Parvanov (dparv) wrote :
Diko Parvanov (dparv)
description: updated
Revision history for this message
Vitaly Antonenko (anvial) wrote :

Looks like this issue is already fixed https://github.com/juju/python-libjuju/pull/612

tags: added: manual-provider
Changed in juju:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.