Comment 7 for bug 1717983

On Tue, Sep 19, 2017 at 01:09:24PM -0000, Scott Moser wrote:
> "I don't know.... I don't think.." doesnt really seem like valid
> justification for marking Invalid on avahi. I went looking a bit
> further. I'm not exactly sure why it ties into dhcp hooks, but it also
> ties into ifupdown hooks.

Ok, so alternate rationale: avahi-autoipd is a service that is primarily of
interest to mobile client systems, not to servers. The ifupdown->networkd
transition only affects servers. On client systems, we will continue to use
NetworkManager, which for the past 9 years has not been running the dhclient
hooks:

  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/293139

And no one has complained in that time about misbehavior of avahi as a
result of these particular hooks not being run. Therefore, whatever the
reason these undocumented upstream hooks were added, I don't believe they
matter for the ifupdown->systemd transition.

If you prefer to express this as 'wontfix' or 'triaged'+'wishlist', I don't
mind. But in terms of prioritization, I don't consider it important to
follow through any further on the avahi dhclient hooks.

> Should I raise another of these bugs for programs that ship ifupdown hooks ?
> /etc/network/if-{up,down}.d/*

I think that's reasonable. But please note that networkd simply does not
support these kinds of hooks today (in particular it does not support
if-pre-up.d and if-down.d because these hooks must block networkd; you can
implement if-up.d and if-post-down.d by running /after/ the network events).
The decision to migrate to networkd has been taken in full knowledge that,
at least initially, there would be regressions in these kinds of
integrations.