You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
systemd version the issue has been seen with
242-7
Used distribution
Debian Unstable
Expected behaviour you didn't see
If I move a network interface out of the main network namespace, the device unit for that network interface should be deactivated, since systemd cannot manage it anymore.
(Alternatively, I would prefer if systemd could keep managing it and keep bound units alive, but from the discussion on #3939 I get the impression that's not how it's supposed to work.)
Unexpected behaviour you saw
If I move a network interface out of the main network namespace, the device unit for that network interface stays active. However, units bound to the device unit do get stopped, which is confusing.
# ip link add testiface type veth
# systemctl start test-device-netns.target
# ip netns add testns
# ip link set testiface netns testns
Then inspect the state of the sys-subsystem-net-devices-testiface.device and test-device-ns.target. The latter is stopped (which is the intended behaviour according to #3939), but the former is still active, which doesn't make a ton of sense.
The text was updated successfully, but these errors were encountered:
systemd version the issue has been seen with
242-7
Used distribution
Debian Unstable
Expected behaviour you didn't see
If I move a network interface out of the main network namespace, the device unit for that network interface should be deactivated, since systemd cannot manage it anymore.
(Alternatively, I would prefer if systemd could keep managing it and keep bound units alive, but from the discussion on #3939 I get the impression that's not how it's supposed to work.)
Unexpected behaviour you saw
If I move a network interface out of the main network namespace, the device unit for that network interface stays active. However, units bound to the device unit do get stopped, which is confusing.
Steps to reproduce the problem
test-device-ns.target
:Run:
Then inspect the state of the
sys-subsystem-net-devices-testiface.device
andtest-device-ns.target
. The latter is stopped (which is the intended behaviour according to #3939), but the former is still active, which doesn't make a ton of sense.The text was updated successfully, but these errors were encountered: