Comment 12 for bug 1416928

I've analyzed the problem and used the given steps to reproduce it.
The issue is due to the way we sort and pick cloud-local addresses for machines (incl. the api server). We should filter out any 10.0.x.y addresses we can see on the machine before considering them as usabled, taking into account the existence and contents of /etc/default/lxc-net (e.g. LXC_ADDR="10.0.3.1" and/or whatever address has the bridge specified in LXC_BRIDGE).

This should solve the problem and it could be easily ported to 1.20, 1.21, 1.22, and trunk. I'll start on the fix.