@Alkis: It's possible that this still affects Xenial even with fixing ifup@.service, as networking.service (which does not do that network file check any more) might also shut down the interfaces; it just does it later on.
But this bears the question why on an LTSP system ifupdown has a configuration for the interface that the root fs is mounted on? This interface is being set up by the initramfs already, via udhcpd; ifupdown should not have a config stanza (or at least only a manual one) for this. How does this work? In particular, what's /etc/network/interfaces and interfaces.d/* on that system?
@Alkis: It's possible that this still affects Xenial even with fixing ifup@.service, as networking.service (which does not do that network file check any more) might also shut down the interfaces; it just does it later on.
But this bears the question why on an LTSP system ifupdown has a configuration for the interface that the root fs is mounted on? This interface is being set up by the initramfs already, via udhcpd; ifupdown should not have a config stanza (or at least only a manual one) for this. How does this work? In particular, what's /etc/network/ interfaces and interfaces.d/* on that system?
Thanks!