This issue hits me again with this SRU cycle (5.3.0-41.33) on the same Eoan s2lp4 node. I had to manually reboot it for SRU tests.
** Tags added: sru-20200217 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860421 Title: Sometime the Eoan s390x LPAR can't get an IP address after reboot Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Node: s2lp4 Ubuntu Eoan s390x LPAR Sometimes after a reboot (we always reboot it before start testing), this instance will lost its network connection. This is not the first time that I saw this issue with Eoan in this SRU cycle. With the most recent respin (5.3.0-29.31) this happened only once. The system is still alive, just the network connection not working. You will have to access it via HMC console and reboot it from there. You will find the dmesg when the networking is not working in the attachment. Here is the ip addr output when this happens: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: encc000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 2a:55:61:1d:aa:38 brd ff:ff:ff:ff:ff:ff inet6 fe80::2855:61ff:fe1d:aa38/64 scope link valid_lft forever preferred_lft forever 3: enP1p0s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 82:0a:2d:0c:b8:70 brd ff:ff:ff:ff:ff:ff 4: enP1p0s0d1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 82:0a:2d:0c:b8:71 brd ff:ff:ff:ff:ff:ff 5: enP2p0s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 82:0a:2d:0c:b7:00 brd ff:ff:ff:ff:ff:ff 6: enP2p0s0d1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 82:0a:2d:0c:b7:01 brd ff:ff:ff:ff:ff:ff 7: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff inet 10.0.3.1/24 scope global lxcbr0 valid_lft forever preferred_lft forever 8: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:4c:f5:88 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 9: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:4c:f5:88 brd ff:ff:ff:ff:ff:ff I don't recall we have this issue before, it might need some more investigation with reboot stress test. The last test suite executed before this issue happens is the "sru- misc-stable" test, it should be executed again to make sure this issue is not caused by tests. BTW, there is a similar bug 1859530 for Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1860421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
