I still cannot reproduce this. In a xenial cloud instance I ran
for i in `seq 50`; do systemctl reset-failed networking; systemctl restart networking;
done
successfully, this is with a standard /etc/network/interfaces.d/50-cloud-init.cfg with just "auto ens3" and "iface ens3 inet dhcp" and no other interface (besides lo).
We can fix this case more centrally in invoke-rc.d though; this is only safe for "reload" and "force-reload", but that will cover this networking/openssh deadlock.
If you can reproduce this, please apply this patch to invoke-rc.d:
I still cannot reproduce this. In a xenial cloud instance I ran
for i in `seq 50`; do systemctl reset-failed networking; systemctl restart networking;
done
successfully, this is with a standard /etc/network/ interfaces. d/50-cloud- init.cfg with just "auto ens3" and "iface ens3 inet dhcp" and no other interface (besides lo).
We can fix this case more centrally in invoke-rc.d though; this is only safe for "reload" and "force-reload", but that will cover this networking/openssh deadlock.
If you can reproduce this, please apply this patch to invoke-rc.d:
sudo patch /usr/sbin/ invoke- rc.d /tmp/invoke- rc.d.patch
and confirm that this fixes it. Thanks!