------- Comment From cdead...@us.ibm.com 2022-07-23 09:55 EDT------- Re-open to move to diff. component.
#=#=# 2015-04-23 10:27:57 (CDT) #=#=# New Fix_Potential = [GSI_HDW] #=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=# Any updates on this issue? Thanks! Some "sync" issue between CQ and bugzilla. Please see the bugzilla: https://bugzilla.linux.ibm.com/show_bug.cgi?id=122308 The approval '*** STG AUTO-GENERATED *** Verify Fix' has been removed because the following condition was met: perform the action Close ** Bug watch added: bugzilla.linux.ibm.com/ #122308 https://bugzilla.linux.ibm.com/show_bug.cgi?id=122308 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1437375 Title: [udev] Adding "Austin" adapter to Ubuntu partition take over system network interface Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Released Status in systemd source package in Vivid: Fix Released Status in systemd source package in Wily: Fix Released Bug description: [Impact] This impacts any user of LPARs; upon adding physical network interfaces (or, realistically, any network interface at all, even virtual), the network interface which is used for system access and used to install the system may not appear in the same order after reboot. [Test Case] Requires access to logical partitions. 1) Install system 2) Add an physical network adapter to the partition 3) Reboot. Observed behavior: After reboot, the virtual adapter expected to be used is unavailable, the address is assigned to any other network adapter which may have been detected and used persistent addresses. Expected behavior The system should come up with network interfaces in the same order as before rebooting. [Regression Potential] Added virtual interfaces that should be not persist (because they are locally administered and thus may have their MAC address change) may come up as persistent devices due to the use of the ibmveth driver, and thus fail to work as expected. --- Problem Description: ==================== Adding Austin adapter to Ubuntu partition took over system network interface. This caused system to be off network connection. ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu Vivid Vervet (development branch) \n \l Kernel Version: 3.18.0-13-generic HTX Version: htxubuntu-322 Host Name: br14p08 Machine Serial No: IBM,0210800E7 Machine Type/Model: IBM,9119-MHE System FW Level: FW830.00 (SC830_021) BEFORE adding Austin adapter to br14p08: ======================================== Before adding austin adapter to br14p05 (vio client), the system network is good. ubuntu@br14p08:~$ lsslot -cpci ubuntu@br14p08:~$ + eth0 U9119.MHE.10800E7-V8-C2-T1 Interpartition Logical LAN root@br14p08:~# lscfg |grep eth + eth0 U9119.MHE.10800E7-V8-C2-T1 root@br14p08:~# ifconfig eth0 Link encap:Ethernet HWaddr 16:59:c0:50:0a:02 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37366 errors:0 dropped:16 overruns:0 frame:0 TX packets:153 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2472739 (2.4 MB) TX bytes:22596 (22.5 KB) Interrupt:19 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@br14p08:~# ping br14p08 PING br14p08.aus.stglabs.ibm.com (9.3.21.12) 56(84) bytes of data. 64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=1 ttl=64 time=0.008 ms 64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=2 ttl=64 time=0.004 ms 64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=3 ttl=64 time=0.005 ms ^C --- br14p08.aus.stglabs.ibm.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.004/0.005/0.008/0.003 ms root@br14p08:~# ping nimitz PING nimitz.aus.stglabs.ibm.com (9.3.165.31) 56(84) bytes of data. 64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=1 ttl=254 time=0.344 ms 64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=2 ttl=254 time=0.326 ms 64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=3 ttl=254 time=0.363 ms ^C AFTER ADDED Austin Adapter: =========================== Once the Austin adapter added to the partition, the Austin's 1st port became eth0. and it pushed the virtual ethernet (which is system's ethernet) to be eth4. However, the system still looking for eth0 as system's main network interface. root@br14p08:~# lscfg | grep eth + eth4 U9119.MHE.10800E7-V8-C2-T1 + eth0 U78CA.001.RCH0133-P1-C2-C1-T1 + eth0 U78CA.001.RCH0133-P1-C2-C1-T1 + eth3 U78CA.001.RCH0133-P1-C2-C1-T2 + ethernet U78CA.001.RCH0133-P1-C2-C1-T3 + eth5 U78CA.001.RCH0133-P1-C2-C1-T4 + eth4 U9119.MHE.10800E7-V8-C2-T1 Interpartition Logical LAN + eth0 U78CA.001.RCH0133-P1-C2-C1-T1 PCIe2 4-port 1GbE Adapter (14105716) + eth0 U78CA.001.RCH0133-P1-C2-C1-T1 Ethernet PCI Adapter + ptp0 U78CA.001.RCH0133-P1-C2-C1-T1 + eth3 U78CA.001.RCH0133-P1-C2-C1-T2 PCIe2 4-port 1GbE Adapter (14105716) + ethernet U78CA.001.RCH0133-P1-C2-C1-T3 PCIe2 4-port 1GbE Adapter (14105716) + eth5 U78CA.001.RCH0133-P1-C2-C1-T4 PCIe2 4-port 1GbE Adapter (14105716) root@br14p08:~# ifconfig eth0 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a0 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::42f2:e9ff:fe5a:33a0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:509 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:32744 (32.7 KB) Interrupt:248 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:258 errors:0 dropped:0 overruns:0 frame:0 TX packets:258 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:28260 (28.2 KB) TX bytes:28260 (28.2 KB) == Comment: #8 - Siraj M. Ismail <sir...@us.ibm.com> - 2015-03-23 16:43:50 == This is a LPAR on a PowerVM system, so no bridge or br0 interfaces on this one. The Virtual adapter is provided by the VIOS server, which shows up as a ethernet port when the LPAR boots up. The issue is that when another adapter with 4 ports gets added to the LPAR with DLPAR add operation while the partition is running, the original eth0 gets renamed to eth5 or similar, and we loose the IP configuration for the LPAR. And that is what need to be looked at and see if this is a driver issue or just a procedure change. Here are some details of what happens on the system: Before adding the adapter: (initial config) ================================ root@br14p08:~# lsslot # Slot Description Linux Name Device(s) U9119.MHE.10800E7-V8-C0 Virtual I/O Slot 30000000 vty U9119.MHE.10800E7-V8-C2 Virtual I/O Slot 30000002 l-lan U9119.MHE.10800E7-V8-C3 Virtual I/O Slot 30000003 v-scsi root@br14p08:~# ethtool -P eth0 Permanent address: 16:59:c0:50:0a:02 <== MAC root@br14p08:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 16:59:c0:50:0a:02 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:375794 errors:0 dropped:1 overruns:0 frame:0 TX packets:9646 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:46210638 (46.2 MB) TX bytes:787820 (787.8 KB) Interrupt:19 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@br14p08:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 9.3.21.12 netmask 255.255.254.0 gateway 9.3.20.1 dns-nameservers 9.3.1.200 dns-search aus.stglabs.ibm.com isst.aus.stglabs.ibm.com After adding a four port Ethernet adapter at runtime: ======================================== Before Reboot: =========== root@br14p08:~# lspci 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) root@br14p08:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 16:59:c0:50:0a:02 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:637083 errors:0 dropped:3 overruns:0 frame:0 TX packets:10943 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:63241734 (63.2 MB) TX bytes:977826 (977.8 KB) Interrupt:19 eth3 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a1 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth4 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a2 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth5 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a3 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) rename6 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) After reboot: ========= root@br14p08:~# lspci 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) root@br14p08:~# lsslot # Slot Description Linux Name Device(s) U9119.MHE.10800E7-V8-C0 Virtual I/O Slot 30000000 vty U9119.MHE.10800E7-V8-C2 Virtual I/O Slot 30000002 l-lan U9119.MHE.10800E7-V8-C3 Virtual I/O Slot 30000003 v-scsi root@br14p08:~# root@br14p08:~# ifconfig eth0 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a0 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::42f2:e9ff:fe5a:33a0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:242 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:15656 (15.6 KB) Interrupt:248 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:123 errors:0 dropped:0 overruns:0 frame:0 TX packets:123 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:13584 (13.5 KB) TX bytes:13584 (13.5 KB) root@br14p08:~# ethtool -P eth0 <= Eth0 has changed to new adapter Permanent address: 40:f2:e9:5a:33:a0 As you can see, port for eth0 has now changed, but the IP address stayed with the port name eth0, whih causes the LPAR to loose it's network. That is the issue we need to address with this bug. == Comment: #9 - Brian J. King <bjki...@us.ibm.com> - 2015-03-23 18:49:15 == It looks like Ubuntu 14.04 by default uses /lib/udev/write_net_rules to modify /etc/udev/rules.d/70-persistent-net.rules in order to do persistent eth device name binding. Looking at /etc/udev/rules.d/70-persistent-net.rules on this system, I see multiple entries for the same mac address, so something may be broken in this script. == Comment: #11 - Siraj M. Ismail <sir...@us.ibm.com> - 2015-03-24 10:19:20 == This is a LPAR on a PowerVM system, so no bridge or br0 interfaces on this one. The Virtual adapter is provided by the VIOS server, which shows up as a ethernet port when the LPAR boots up. The issue is that when another adapter with 4 ports gets added to the LPAR with DLPAR add operation while the partition is running, the original eth0 gets renamed to eth5 or similar, and we loose the IP configuration for the LPAR. And that is what need to be looked at and see if this is a driver issue or just a procedure change. Here are some details of what happens on the system: Before adding the adapter: (initial config) ================================ root@br14p08:~# lsslot # Slot Description Linux Name Device(s) U9119.MHE.10800E7-V8-C0 Virtual I/O Slot 30000000 vty U9119.MHE.10800E7-V8-C2 Virtual I/O Slot 30000002 l-lan U9119.MHE.10800E7-V8-C3 Virtual I/O Slot 30000003 v-scsi root@br14p08:~# ethtool -P eth0 Permanent address: 16:59:c0:50:0a:02 <== MAC root@br14p08:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 16:59:c0:50:0a:02 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:375794 errors:0 dropped:1 overruns:0 frame:0 TX packets:9646 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:46210638 (46.2 MB) TX bytes:787820 (787.8 KB) Interrupt:19 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@br14p08:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 9.3.21.12 netmask 255.255.254.0 gateway 9.3.20.1 dns-nameservers 9.3.1.200 dns-search aus.stglabs.ibm.com isst.aus.stglabs.ibm.com After adding a four port Ethernet adapter at runtime: ======================================== Before Reboot: =========== root@br14p08:~# lspci 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) root@br14p08:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 16:59:c0:50:0a:02 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:637083 errors:0 dropped:3 overruns:0 frame:0 TX packets:10943 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:63241734 (63.2 MB) TX bytes:977826 (977.8 KB) Interrupt:19 eth3 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a1 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth4 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a2 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth5 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a3 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) rename6 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) After reboot: ========= root@br14p08:~# lspci 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) root@br14p08:~# lsslot # Slot Description Linux Name Device(s) U9119.MHE.10800E7-V8-C0 Virtual I/O Slot 30000000 vty U9119.MHE.10800E7-V8-C2 Virtual I/O Slot 30000002 l-lan U9119.MHE.10800E7-V8-C3 Virtual I/O Slot 30000003 v-scsi root@br14p08:~# root@br14p08:~# ifconfig eth0 Link encap:Ethernet HWaddr 40:f2:e9:5a:33:a0 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::42f2:e9ff:fe5a:33a0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:242 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:15656 (15.6 KB) Interrupt:248 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:123 errors:0 dropped:0 overruns:0 frame:0 TX packets:123 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:13584 (13.5 KB) TX bytes:13584 (13.5 KB) root@br14p08:~# ethtool -P eth0 <= Eth0 has changed to new adapter Permanent address: 40:f2:e9:5a:33:a0 As you can see, port for eth0 has now changed, but the IP address stayed with the port name eth0, whih causes the LPAR to loose it's network. That is the issue we need to address with this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1437375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
