[Bug 1087228] Re: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if-post-down.d/bind9
Opinion is a closing state for things that won't get fixed, please avoid using it unless you actually mean it :) This is clearly a bug, describing a race condition causing problems with essential part of Ubuntu (resolvconf), so I'm changing this to Triaged and Medium (as it doesn't seem to be causing horrible breakage). ** Changed in: bind9 (Ubuntu) Status: Opinion = Triaged ** Changed in: bind9 (Ubuntu) Importance: Wishlist = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1087228 Title: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if- post-down.d/bind9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1087228/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1087228] Re: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if-post-down.d/bind9
Thanks, Stéphane. It doesn't actually affect resolvconf — sorry if I gave that impression. Because it is only the down script that is run at the wrong time (it is currently run at pre-down time instead of post-down time), the effect of the bug is minor: it only means that named is listening on the address of an interface that has since been deconfigured. Of course, if the admin customizes the script, misled into thinking that it gets run at post-down time (as it apparently should be) then it could become a bit more serious. ** Summary changed: - /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if-post-down.d/bind9 + The rndc reconfig in /etc/network/if-down.d/bind9 should be in /etc/network/if-post-down.d/bind9 ** Description changed: The bind9 package includes /etc/network/if-down.d/bind9 which does rndc reconfig. But this should only be done *after* the interface has been deconfigured not before. NetworkManager's /etc/NetworkManager/dispatcher.d/01ifupdown run-partses only /etc/network/if-up.d and /etc/network/if-post-down.d, so when an interface is deconfigured using NetworkManager the bind9 hook script doesn't get run at all; named does not notice that the interface has been deconfigured until its next poll (which happens every 60 minutes by default). - It looks to me as if /etc/network/if-down.d/bind9 should be moved to - /etc/network/if-post-down.d/. + It looks to me as if the rndc reconfig in /etc/network/if-down.d/bind9 + should be moved into /etc/network/if-post-down.d/. bind 9 1:9.8.1.dfsg.P1-4.2ubuntu3 ** Description changed: The bind9 package includes /etc/network/if-down.d/bind9 which does rndc reconfig. But this should only be done *after* the interface has been deconfigured not before. NetworkManager's /etc/NetworkManager/dispatcher.d/01ifupdown run-partses only /etc/network/if-up.d and /etc/network/if-post-down.d, so when an interface is deconfigured using NetworkManager the bind9 hook script doesn't get run at all; named does not notice that the interface has been deconfigured until its next poll (which happens every 60 minutes by default). It looks to me as if the rndc reconfig in /etc/network/if-down.d/bind9 - should be moved into /etc/network/if-post-down.d/. + should be moved into /etc/network/if-post-down.d/bind9. bind 9 1:9.8.1.dfsg.P1-4.2ubuntu3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1087228 Title: The rndc reconfig in /etc/network/if-down.d/bind9 should be in /etc/network/if-post-down.d/bind9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1087228/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1087228] Re: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if-post-down.d/bind9
This report has been downgraded to wishlist opinion. Very well, Yolanda, but please accompany that change with some sort of explanation. Bind9's ifdown hook script does rndc reconfig which causes named to notice changes that have been made. If the script is run *before* taking down the interface then it is run when no changes have yet been made, so it has no effect. Immediately after this, ifdown takes down the interface, but nothing causes named to notice this change. This behavior was noticed in the real world and can easily be reproduced. Thus in my opinion this is an obvious bug and I wish it to be fixed ASAP. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1087228 Title: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if- post-down.d/bind9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1087228/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1087228] Re: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if-post-down.d/bind9
** Changed in: bind9 (Ubuntu) Status: New = Opinion ** Changed in: bind9 (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1087228 Title: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if- post-down.d/bind9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1087228/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1087228] Re: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if-post-down.d/bind9
All very well to classify this as a wishlist opinion, but please accompany that with some sort of reasoning. Bind9's ifdown hook script does rndc reconfig which causes named to notice changes that have been made. If the script is run *before* taking down the interface then it is run when no changes have yet been made, so it has no effect. Immediately after this, ifdown takes down the interface, but nothing causes named to notice this change. This behavior was noticed in the real world and can easily be reproduced. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1087228 Title: /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if- post-down.d/bind9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1087228/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
