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@br0`, br0 goes down but doesn't come
back up. It prints this error:
A dependency job for [email protected] failed. See 'journalctl -xe'
for details.
The command `systemctl status ifup@br0` says (in part):
Mar 13 15:09:10 example.com systemd[1]: [email protected]: 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]: [email protected]: Job
[email protected]/start failed with result 'dependency'.
The lines in /lib/systemd/system/[email protected] 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
Touch seeded packages, 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@br0`, br0 goes down but doesn't come
back up. It prints this error:
A dependency job for [email protected] failed. See 'journalctl -xe'
for details.
The command `systemctl status ifup@br0` says (in part):
Mar 13 15:09:10 example.com systemd[1]: [email protected]: 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]: [email protected]: Job
[email protected]/start failed with result 'dependency'.
The lines in /lib/systemd/system/[email protected] 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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
