Ubuntu
network-manager package

  1. Bug #1790098
  2. Comment #6

Comment 6 for bug 1790098

Revision history for this message
Steve Langasek (vorlon) wrote :

Test repeated on an Ubuntu 18.04 s390x container (Ubuntu 18.04 host):

# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
6: bond0.100@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 10.242.92.157/24 brd 10.242.92.255 scope global bond0.100
       valid_lft forever preferred_lft forever
# ip link set dev bond0 down
# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
# ip link set dev bond0 up
# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
6: bond0.100@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 10.242.92.157/24 brd 10.242.92.255 scope global bond0.100
       valid_lft forever preferred_lft forever
# uname -a
Linux enhanced-warthog 4.17.0-9-generic #10-Ubuntu SMP Wed Aug 22 13:31:35 UTC 2018 s390x s390x s390x GNU/Linux
#

No indication of behavior difference on Ubuntu 18.04 s390x.