Bug#809166: networking.service does not prevent ifdown with network file systems

[Guus Sliepen]

On Mon, Dec 28, 2015 at 08:13:18AM +0100, Martin Pitt wrote:

> > Please check if the problem still exists with version 0.8.4. Version 0.8
> > didn't correctly order itself with respect to network-online.target, but
> > 0.8.4 should have fixed that.
> 
> This should be unrelated to network-online.target. networking.service
> has "Conflicts=shutdown.target" and thus will always be stopped during
> shutdown/reboot, you can see
> 
>   [  OK  ] Stopped Raise network interfaces.
> 
> So with NFS or iscsi this will now mean that shutdown will be rather
> broken/hanging after that point.

Hm, but shouldn't systemd (with networking.service from ifupdown 0.8.4)
order the unmounting of the NFS/iSCSI partitions before stoppping the
network interfaces?

> So maybe the effects with this are bearable, I didn't yet investigate
> it on an actually affected system. So please feel free to close if you
> are convinced that this check isn't necessary any more, I mostly filed
> this as a reminder.

That's fine, I'll keep it open until it's confirmed that the issue is
fixed. But I would like the solution to be that systemd, given correct
information in the .service files, correctly orders everything, rather
than hacking ifupdown itself to work around this problem.

-- 
Met vriendelijke groet / with kind regards,
      Guus Sliepen <guus at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151228/846e42ce/attachment-0002.sig>