Sometime the Eoan s390x LPAR can't get an IP address after reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
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,
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,
link/ether 2a:55:61:1d:aa:38 brd ff:ff:ff:ff:ff:ff
inet6 fe80::2855:
valid_lft forever preferred_lft forever
3: enP1p0s0: <BROADCAST,
link/ether 82:0a:2d:0c:b8:70 brd ff:ff:ff:ff:ff:ff
4: enP1p0s0d1: <BROADCAST,
link/ether 82:0a:2d:0c:b8:71 brd ff:ff:ff:ff:ff:ff
5: enP2p0s0: <BROADCAST,
link/ether 82:0a:2d:0c:b7:00 brd ff:ff:ff:ff:ff:ff
6: enP2p0s0d1: <BROADCAST,
link/ether 82:0a:2d:0c:b7:01 brd ff:ff:ff:ff:ff:ff
7: lxcbr0: <NO-CARRIER,
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,
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,
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.
tags: | added: eoan s390x |
tags: | added: 5.3 |
description: | updated |
tags: | added: sru-20200106 |
description: | updated |
Changed in ubuntu-kernel-tests: | |
status: | New → Triaged |
assignee: | nobody → Sean Feole (sfeole) |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1860421
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.