Bug#901834: systemd-networkd block the shutdown process of my nspawn container

[Michael Biebl]

On Mon, 07 Nov 2016 13:05:44 +0800 Zhang Jingqiang <zh_jq at outlook.com>
wrote:
> Package: systemd
> Version: 232-2
> Severity: normal
> 
> Hello,
> I have a nspawn container, which has one bridged interface and one veth local only interface,
> which is called as "host0" and "ho" in the container.
> The command to start the container by the service file is
> 
>  #/usr/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth -U --settings=override --machine=pstat-ci
> 
> The config file pstat-ci.nspawn is
>   [Exec]
>   Boot=on
>   User=root
>   PrivateUsers=off
> 
>   [Network]
>   Bridge=br0
>   VirtualEthernetExtra=nspawn:ho
> 
> I add systemd-networkd config files in the container as follow:
>  /etc/systemd/network/80-dhcp.network:
>   [Match]
>   Name=host*
> 
>   [Network]
>   DHCP=ipv4
> 
>  /etc/systemd/network/80-static.network:
>   [Match]
>   Name=ho
> 
>   [Network]
>   Address=192.168.2.2/24
> 
>   [Route]
>   Gateway=192.168.2.1
>   Scope=link
> 
> When I stop the coresponding nspawn service, timeout happened, with log in the container like this:
>   Nov 07 12:26:32 pstat-ci systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
>   Nov 07 12:26:32 pstat-ci systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
>   Nov 07 12:26:32 pstat-ci systemd[1]: systemd-networkd.service: Unit entered failed state.
>   Nov 07 12:26:32 pstat-ci systemd[1]: Failed to start Network Service.
>   Nov 07 12:26:32 pstat-ci systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
>   Nov 07 12:26:32 pstat-ci systemd[1]: Stopped target Local File Systems (Pre).
>   Nov 07 12:26:32 pstat-ci systemd[1]: Reached target Final Step.
>   Nov 07 12:26:32 pstat-ci systemd[1]: Reached target Unmount All Filesystems.
>   Nov 07 12:26:32 pstat-ci systemd-networkd[130]: Could not connect to bus: Connection refused
> 
> And the service stop action takes about 90s to finish.
> 
> After I disabled systemd-networkd, and use interfaces(5) to config network, the service stop action finish
> in time, no more that 30s.
> 
> dbus is installed in the container.

This sounds like it could be the same issue as in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901834

Zhang Jingqiang, could you please test the patch that posted by Tobias
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901834#5

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180623/7b12822a/attachment-0002.sig>