Bug#928984: ifupdown: networking lost when installing ifupdown2
On Fri, Sep 20, 2019 at 5:14 PM Guus Sliepen wrote: > On Tue, May 14, 2019 at 03:35:07PM +, George Diamantopoulos wrote: > > > I'm not sure if this bug should be filed against ifupdown or ifupdown2. > > This issue only seems to affect current versions of these packages > > in buster, I haven't encountered this in stretch. > > > > When installing ifupdown2, apt will remove ifupdown before proceeding > with > > installation of ifupdown2 as the two cannot co-exist on the same system. > > This is a bit tricky. Especially with systemd, there is no easy way to > say "please stop this service but don't execute its ExecStop command". > Also, properly shutting down the network will be nicer for ifupdown2, > because if ifupdown doesn't shut down cleanly, ifupdown2 might not start > in an orderly way. > > > When issuing the command to install ifupdown2 over SSH the issue can be > > quite easily worked around by restarting the networking service > immediately > > after ifupdown2 is installed: > > apt-get install ifupdown2 && systemctl restart networking > > > > However, there seems to be no simple solution when using configuration > > management (like ansible) to install ifupdown2. The relevant tasks will > > hang forever upon ifupdown2 installation. > > For provisioning systems like ansible, puppet etc., I recommend that you > set it up to push a script to the node that basically executes the > equivalent of "apt-get install ifupdown2 && systemctl restart > networking" using nohup or something else to make it not fail if the > network itself is down. > I wouldn't recommend doing a restart networking unless you are sure that your configuration file is compatible with ifupdown2. We should support most of ifupdown syntax though but you may loose connectivity. Instead you may consider running ifreload: apt-get install ifupdown2 && ifreload -a > On the other hand, if ifupdown2 would automatically start the network at > install time, you wouldn't need the systemctl command to restart the > network. Maybe that is enough to fix this issue? I'm Cc'ing the > maintainer of ifupdown2. > This is a possibility that i'm considering as well. > > -- > Met vriendelijke groet / with kind regards, > Guus Sliepen >
Bug#928984: ifupdown: networking lost when installing ifupdown2
On Tue, May 14, 2019 at 03:35:07PM +, George Diamantopoulos wrote: > I'm not sure if this bug should be filed against ifupdown or ifupdown2. > This issue only seems to affect current versions of these packages > in buster, I haven't encountered this in stretch. > > When installing ifupdown2, apt will remove ifupdown before proceeding with > installation of ifupdown2 as the two cannot co-exist on the same system. This is a bit tricky. Especially with systemd, there is no easy way to say "please stop this service but don't execute its ExecStop command". Also, properly shutting down the network will be nicer for ifupdown2, because if ifupdown doesn't shut down cleanly, ifupdown2 might not start in an orderly way. > When issuing the command to install ifupdown2 over SSH the issue can be > quite easily worked around by restarting the networking service immediately > after ifupdown2 is installed: > apt-get install ifupdown2 && systemctl restart networking > > However, there seems to be no simple solution when using configuration > management (like ansible) to install ifupdown2. The relevant tasks will > hang forever upon ifupdown2 installation. For provisioning systems like ansible, puppet etc., I recommend that you set it up to push a script to the node that basically executes the equivalent of "apt-get install ifupdown2 && systemctl restart networking" using nohup or something else to make it not fail if the network itself is down. On the other hand, if ifupdown2 would automatically start the network at install time, you wouldn't need the systemctl command to restart the network. Maybe that is enough to fix this issue? I'm Cc'ing the maintainer of ifupdown2. -- Met vriendelijke groet / with kind regards, Guus Sliepen signature.asc Description: PGP signature
Bug#928984: ifupdown: networking lost when installing ifupdown2
Package: ifupdown Version: 0.8.35 Severity: important Dear Maintainer, I'm not sure if this bug should be filed against ifupdown or ifupdown2. This issue only seems to affect current versions of these packages in buster, I haven't encountered this in stretch. When installing ifupdown2, apt will remove ifupdown before proceeding with installation of ifupdown2 as the two cannot co-exist on the same system. The problem seems to be that, following removal of ifupdown, the networking service is stopped, and the host loses all connectivity. This behaviour is potentially debilitating, especially when the task is performed via SSH or via configuration management software which depends on the host being reachable over the network to operate. When issuing the command to install ifupdown2 over SSH the issue can be quite easily worked around by restarting the networking service immediately after ifupdown2 is installed: apt-get install ifupdown2 && systemctl restart networking However, there seems to be no simple solution when using configuration management (like ansible) to install ifupdown2. The relevant tasks will hang forever upon ifupdown2 installation. Is this deliberate? Any chance you can reconsider the actions taken upon uninstallation of ifupdown? Thank you. Best regards, George Diamantopoulos -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.118 ii iproute2 4.20.0-2 ii libc6 2.28-10 ii lsb-base 10.2019031300 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.4.1-2 Versions of packages ifupdown suggests: pn ppp pn rdnssd -- Configuration Files: /etc/default/networking changed [not included] /etc/init.d/networking changed [not included]
