[Bug 2011484] [NEW] ifup@%i.service systemd unit file can't be restarted for br0 device

[CH]

Public bug reported:

On Ubuntu 20.04 and 22.04, we've configured a bridged device (br0) in
/etc/network/interfaces like this:

auto br0
iface br0 inet static
        address 172.16.201.5
        netmask 255.255.255.0
        broadcast 172.16.201.255
        bridge_ports none

If we run `ifup br0` or `ifdown br0`, everything works perfectly.

If we run `systemctl restart ifup at br0`, br0 goes down but doesn't come
back up. It prints this error:

    A dependency job for ifup at br0.service failed. See 'journalctl -xe'
for details.

The command `systemctl status ifup at br0` says (in part):

    Mar 13 15:09:10 example.com systemd[1]: ifup at br0.service: Bound to unit sys-subsystem-net-devices-br0.device, but unit isn't active.
    Mar 13 15:09:10 example.com systemd[1]: Dependency failed for ifup for br0.
    Mar 13 15:09:10 example.com systemd[1]: ifup at br0.service: Job ifup at br0.service/start failed with result 'dependency'.

The lines in /lib/systemd/system/ifup at .service that seem to be causing
the problem are:

    BindsTo=sys-subsystem-net-devices-%i.device
    After=sys-subsystem-net-devices-%i.device

Versions tested+affected:
    ifupdown/jammy,now 0.8.36+nmu1ubuntu3 amd64 [installed]
    ifupdown/focal,now 0.8.35ubuntu1 amd64 [installed]

Our workaround is to use `ifdown br0` and `ifup br0`, but it'd be nice
if systemd could handle it.

Thanks

** Affects: ifupdown (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/2011484

Title:
  ifup@%i.service systemd unit file can't be restarted for br0 device

Status in ifupdown package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04 and 22.04, we've configured a bridged device (br0) in
  /etc/network/interfaces like this:

  auto br0
  iface br0 inet static
          address 172.16.201.5
          netmask 255.255.255.0
          broadcast 172.16.201.255
          bridge_ports none

  If we run `ifup br0` or `ifdown br0`, everything works perfectly.

  If we run `systemctl restart ifup at br0`, br0 goes down but doesn't come
  back up. It prints this error:

      A dependency job for ifup at br0.service failed. See 'journalctl -xe'
  for details.

  The command `systemctl status ifup at br0` says (in part):

      Mar 13 15:09:10 example.com systemd[1]: ifup at br0.service: Bound to unit sys-subsystem-net-devices-br0.device, but unit isn't active.
      Mar 13 15:09:10 example.com systemd[1]: Dependency failed for ifup for br0.
      Mar 13 15:09:10 example.com systemd[1]: ifup at br0.service: Job ifup at br0.service/start failed with result 'dependency'.

  The lines in /lib/systemd/system/ifup at .service that seem to be causing
  the problem are:

      BindsTo=sys-subsystem-net-devices-%i.device
      After=sys-subsystem-net-devices-%i.device

  Versions tested+affected:
      ifupdown/jammy,now 0.8.36+nmu1ubuntu3 amd64 [installed]
      ifupdown/focal,now 0.8.35ubuntu1 amd64 [installed]

  Our workaround is to use `ifdown br0` and `ifup br0`, but it'd be nice
  if systemd could handle it.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2011484/+subscriptions