autopkgtests all fail on s390x
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Dan Streetman | ||
Xenial |
Fix Committed
|
Medium
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Dan Streetman | ||
Disco |
Won't Fix
|
Medium
|
Dan Streetman | ||
Eoan |
Fix Released
|
Medium
|
Dan Streetman | ||
Focal |
Fix Released
|
Medium
|
Dan Streetman |
Bug Description
[impact]
all autopkgtests fail on s390x
[test case]
check autopkgtest logs, e.g.
http://
autopkgtest [00:19:32]: @@@@@@@
wpa-dhclient FAIL non-zero exit status 1
nm.py FAIL non-zero exit status 1
killswitches-
urfkill-integration FAIL non-zero exit status 1
[regression potential]
this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that.
[other info]
as mentioned in comment 2, wireless networking is specifically excluded on s390 systems:
menuconfig WIRELESS
bool "Wireless"
depends on !S390
default y
The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-
However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests.
Changed in network-manager (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in network-manager (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in network-manager (Ubuntu Focal): | |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in network-manager (Ubuntu Bionic): | |
importance: | Undecided → Medium |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in network-manager (Ubuntu Eoan): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in network-manager (Ubuntu Xenial): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in network-manager (Ubuntu Disco): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in network-manager (Ubuntu Eoan): | |
importance: | Undecided → Medium |
Changed in network-manager (Ubuntu Disco): | |
importance: | Undecided → Medium |
Changed in network-manager (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in network-manager (Ubuntu Disco): | |
status: | New → In Progress |
Changed in network-manager (Ubuntu Eoan): | |
status: | New → In Progress |
Changed in network-manager (Ubuntu Focal): | |
assignee: | nobody → Dan Streetman (ddstreet) |
description: | updated |
description: | updated |
description: | updated |
tags: | added: block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial |
tags: | removed: block-proposed-eoan |
Changed in network-manager (Ubuntu Xenial): | |
assignee: | Dan Streetman (ddstreet) → nobody |
Most of the failures are due to s390x kernel configuration setting RFKILL=n