[Bug 1860421] Re: Sometime the Eoan s390x LPAR can't get an IP address after reboot
Eoan LPAR upgraded to Focal, thus I am closing this bug. Thanks ** Changed in: ubuntu-kernel-tests Status: Triaged => Invalid ** Changed in: ubuntu-kernel-tests Assignee: Sean Feole (sfeole) => (unassigned) ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860421 Title: Sometime the Eoan s390x LPAR can't get an IP address after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1860421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860421] Re: Sometime the Eoan s390x LPAR can't get an IP address after reboot
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860421 Title: Sometime the Eoan s390x LPAR can't get an IP address after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1860421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860421] Re: Sometime the Eoan s390x LPAR can't get an IP address after reboot
I was able to reboot the lpar a number of 10 times without seeing an interrupt on the network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860421 Title: Sometime the Eoan s390x LPAR can't get an IP address after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1860421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860421] Re: Sometime the Eoan s390x LPAR can't get an IP address after reboot
The correct network device to be used for all testing should be encc000.2586 , verified The netplan yaml is correct, I don't see problems with it. It will explicitly tell the host to use the static IPv4 address I need logs at the time of the failure, unfortunately I feel that resetting the lpar did fix the network, but also erased any useful information pertaining to why the network did not come up. We will need some additional information at the time of the failure. I've restarted the testing for Focal S2lp4 and see if we can reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860421 Title: Sometime the Eoan s390x LPAR can't get an IP address after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1860421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860421] Re: Sometime the Eoan s390x LPAR can't get an IP address after reboot
e i meant Eoan, s390x s2lp4, not focal.. sorry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860421 Title: Sometime the Eoan s390x LPAR can't get an IP address after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1860421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860421] Re: Sometime the Eoan s390x LPAR can't get an IP address after reboot
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860421 Title: Sometime the Eoan s390x LPAR can't get an IP address after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1860421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860421] Re: Sometime the Eoan s390x LPAR can't get an IP address after reboot
** Description changed: 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 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: 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 + 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: 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 + 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: 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 + link/ether 82:0a:2d:0c:b8:70 brd ff:ff:ff:ff:ff:ff 4: enP1p0s0d1: 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 + link/ether 82:0a:2d:0c:b8:71 brd ff:ff:ff:ff:ff:ff 5: enP2p0s0: 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 + link/ether 82:0a:2d:0c:b7:00 brd ff:ff:ff:ff:ff:ff 6: enP2p0s0d1: 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 + link/ether 82:0a:2d:0c:b7:01 brd ff:ff:ff:ff:ff:ff 7: lxcbr0: 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 + 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: 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 + 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: 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 + 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. ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: sru-20200106 ** Description changed: 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: 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: 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: 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:
[Bug 1860421] Re: Sometime the Eoan s390x LPAR can't get an IP address after reboot
ip addr output when the network is good: 1: lo: 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: 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: 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: 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: 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: 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: encc000.2586@encc000: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 2a:55:61:1d:aa:38 brd ff:ff:ff:ff:ff:ff inet 10.245.80.42/22 brd 10.245.83.255 scope global encc000.2586 valid_lft forever preferred_lft forever inet6 fe80::2855:61ff:fe1d:aa38/64 scope link valid_lft forever preferred_lft forever 8: lxcbr0: 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 9: virbr0: 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 10: virbr0-nic: 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 The difference is here: 7: encc000.2586@encc000: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 2a:55:61:1d:aa:38 brd ff:ff:ff:ff:ff:ff inet 10.245.80.42/22 brd 10.245.83.255 scope global encc000.2586 valid_lft forever preferred_lft forever inet6 fe80::2855:61ff:fe1d:aa38/64 scope link valid_lft forever preferred_lft forever ** Attachment added: "dmesg-network-ok.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860421/+attachment/5321891/+files/dmesg-network-ok.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860421 Title: Sometime the Eoan s390x LPAR can't get an IP address after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1860421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
