This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4
---------------
network-manager (1.10.6-2ubuntu1.4) bionic; urgency=medium
* d/p/start-ip-conf-when-master-carrier-goes-up.patch: device: start IP
configuration when master carrier goes up (LP: #1794478)
network-manager (1.10.6-2ubuntu1.3) bionic; urgency=medium
* d/t/control: nm test requires dnsmasq-base (LP: #1850267)
* d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm, d/t/control:
- skip tests on s390 due to missing wireless kernel support
(LP: #1855009)
-- Seyeong Kim <seyeong....@canonical.com> Wed, 19 Feb 2020 14:59:10
+0900
** Changed in: network-manager (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1855009
Title:
autopkgtests all fail on s390x
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
Fix Committed
Status in network-manager source package in Bionic:
Fix Released
Status in network-manager source package in Disco:
Won't Fix
Status in network-manager source package in Eoan:
Fix Released
Status in network-manager source package in Focal:
Fix Released
Bug description:
[impact]
all autopkgtests fail on s390x
[test case]
check autopkgtest logs, e.g.
http://autopkgtest.ubuntu.com/packages/network-manager
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/s390x/n/network-
manager/20191130_001946_a5512@/log.gz
autopkgtest [00:19:32]: @@@@@@@@@@@@@@@@@@@@ summary
wpa-dhclient FAIL non-zero exit status 1
nm.py FAIL non-zero exit status 1
killswitches-no-urfkill FAIL non-zero exit status 1
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-no-urfkill' and 'urfkill-integration' require rfkill
which requires wireless, so none of those tests are valid on s390x,
since it doesn't have any wireless support.
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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
