On 05/02/15 20:56, Dimiter Naydenov wrote: > Hey Tim, > > I'm sorry the networker is causing trouble for you guys. It was > causing issues for us in MaaS and EC2 as well, there were several > fixes to reduce the networker's impact and in fact it is now totally > disabled on trunk. It will stay that way until we have time to fix it > properly. > > However, the networker even in 1.21 is only causing issues when > modifying /etc/network/interfaces inappropriately it *does not* decide > what addresses a machine should use or modifies them in any way. > That's done by the machiner. The networker just discovers the NICs on > the machine and watches in-state NIC documents for changes.
The problem is that it also finds the NICs that were created by lxc and libvirt, both of which use private network range addresses that juju erroneously decides are cloud-private. > We can backport the fix that totally disables the networker to 1.22 > and 1.21 as well, which will require a point release for 1.21. I think we should disable in 1.21 and 1.22 if it has been disabled in master until we adjust the heuristics. Tim -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
