init.d/quagga has erroneous $remote_fs in LSB headers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
quagga (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
The LSB headers for quagga init script has $remote_fs in Required-Start and Required-Stop fields. This means that NFS mounts should be started before quagga sets the IP addresses on the machine, and causes NFS/netdev mounting to fail during the boot process on Trusty systems, due to insserv applying dependencies.
This causes a similar, but related, issue on Xenial where systemd generates a service file that has a similar requirement in it. Debugging that raised the awareness of this particular issue - although upstream appears to be systemd-specific, so newer package versions for Xenial may resolve this issue.
Package version is 0.99.22.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Doesn't this depend on the way round your particular setup is? It makes sense to depend on $remote_fs if your system requires it to boot, for example, and the access to the remote filesystems is _not_ over the network that is managed by quagga. I'd expect this to be the normal case, as it seems like quite a bit of server overloading to be putting quagga on the same instance as something serving files, for example.
You edit files in /etc directly to suit your specific needs; packaging is designed not to stomp on your changes.
Therefore it's not clear to me that this is a bug; rather it's just that the default configuration shipped is the opposite of what you happen to need in your particular case.
Accordingly I'm setting the status to Incomplete, but if you disagree, please feel free to explain and reopen.