I took a look at this bug today since it's bubbling up to the critical level.
I could easily reproduce it (trusty + a 3.18 kernel). I noticed that, after juju does the ifdown, dhclient is still running for the primary interface. Even if ifdown successfully deconfigured the interface, dhclient is just going to bring it back up/configure it when it refreshes its lease. So the question is, why didn't ifdown kill dhclient? Well, I looked at the juju code and I see that it generates a new /e/n/interfaces file before running ifdown. I've experienced issues with this before. I don't believe that ifdown keeps track of how interfaces were brought up itself, it instead consults /e/n/interfaces again. Since /e/n/i was already updated, ifdown doesn't know how the primary interface was brought up, so fails to bring it down cleanly. My suggestion is to bring down the primary interface *before* updating /e/n/i, then bring up the bridge after. ** Patch added: "juju-ifdown-before-updating-eni.patch" https://bugs.launchpad.net/ubuntu/+bug/1496972/+attachment/4503415/+files/juju-ifdown-before-updating-eni.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496972 Title: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
