Comment 23 for bug 1473069

For the VIRBR0 portion of the bug, that should be addressed as bug #1644429 which has a patch in 2.1 and 2.2 right now.

For the SSH keys being rejected, we have bug #1646329 which also should have a patch in 2.1 (there is a proposed fix, which is being reviewed.)

As for the overall "what IP address should be reported for machines that have >1 address", that is still a bit more up in the air, because any sort of heuristic feels like it will be wrong when you ask from a different point of view.

I haven't fully understood what the address ordering is, because some of the original statements (the lowest valued IP address), don't fit what I've seen. Namely that any given MAAS node will return the same order (surviving through a destroy-controller && bootstrap cycle), but the order between nodes is not the same. (node 2 gave ens3 and then ens4, node 3 gave ens4 and then ens3).

Some of this gets better with containers only joining spaces that they have been explicitly requested, as then they won't have IP addresses for all spaces (which is a 2.1 patch). They still are likely to have >1 IP address. Using a heuristic like "What is the PXE network" is particularly poor once you are dealing with containers, because there is no particular reason to expect that they will even need to be on the PXE network.

It is possible that we could model some sort of "space priority", so that for a given space, addresses from that space sort earlier/later than addresses from other spaces.

One thing we're trying to address for 2.1 is that "juju show-machine X" will show you all of the IP addresses for that machine, clustered by what space they are in. I'm not sure if that patch will land in time (tracked as bug #1653997).

That still doesn't handle the case of "what does tabular status show".