| 2019-12-03 22:37:52 |
Dan Streetman |
bug |
|
|
added bug |
| 2019-12-03 22:38:21 |
Dan Streetman |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Xenial) |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Eoan) |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Bionic) |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
nominated for series |
|
Ubuntu Focal |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Focal) |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
nominated for series |
|
Ubuntu Disco |
|
| 2019-12-03 22:38:21 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Disco) |
|
| 2019-12-03 22:38:50 |
Dan Streetman |
network-manager (Ubuntu Xenial): status |
New |
In Progress |
|
| 2019-12-03 22:38:52 |
Dan Streetman |
network-manager (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-12-03 22:38:56 |
Dan Streetman |
network-manager (Ubuntu Focal): status |
New |
In Progress |
|
| 2019-12-03 22:39:03 |
Dan Streetman |
network-manager (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2019-12-03 22:39:08 |
Dan Streetman |
network-manager (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-12-03 22:39:22 |
Dan Streetman |
network-manager (Ubuntu Bionic): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-12-03 22:39:28 |
Dan Streetman |
network-manager (Ubuntu Eoan): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-12-03 22:39:28 |
Dan Streetman |
network-manager (Ubuntu Xenial): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-12-03 22:39:30 |
Dan Streetman |
network-manager (Ubuntu Disco): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-12-03 22:39:39 |
Dan Streetman |
network-manager (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2019-12-03 22:39:40 |
Dan Streetman |
network-manager (Ubuntu Disco): importance |
Undecided |
Medium |
|
| 2019-12-03 22:39:42 |
Dan Streetman |
network-manager (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2019-12-03 22:39:44 |
Dan Streetman |
network-manager (Ubuntu Disco): status |
New |
In Progress |
|
| 2019-12-03 22:39:46 |
Dan Streetman |
network-manager (Ubuntu Eoan): status |
New |
In Progress |
|
| 2019-12-03 22:39:57 |
Dan Streetman |
network-manager (Ubuntu Focal): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-12-04 19:57:40 |
Dan Streetman |
description |
[impact]
most or 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
[regression potential]
TBD |
[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]
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. |
|
| 2019-12-04 19:58:34 |
Dan Streetman |
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]
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. |
[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. |
|
| 2019-12-04 20:00:35 |
Dan Streetman |
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. |
[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. |
|
| 2019-12-06 13:14:18 |
Dan Streetman |
tags |
|
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial |
|
| 2019-12-06 19:48:15 |
Brian Murray |
network-manager (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2019-12-06 19:48:19 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-12-06 19:48:21 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2019-12-06 19:48:25 |
Brian Murray |
tags |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-needed verification-needed-eoan |
|
| 2019-12-06 20:29:12 |
Launchpad Janitor |
network-manager (Ubuntu Focal): status |
In Progress |
Fix Released |
|
| 2019-12-06 21:02:42 |
Brian Murray |
network-manager (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
| 2019-12-06 21:02:48 |
Brian Murray |
tags |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-needed verification-needed-eoan |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-needed verification-needed-disco verification-needed-eoan |
|
| 2019-12-06 21:10:22 |
Brian Murray |
network-manager (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-12-06 21:10:31 |
Brian Murray |
tags |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-needed verification-needed-disco verification-needed-eoan |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan |
|
| 2019-12-06 21:14:53 |
Brian Murray |
network-manager (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2019-12-06 21:15:02 |
Brian Murray |
tags |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan verification-needed-xenial |
|
| 2019-12-07 16:11:29 |
Dan Streetman |
tags |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan verification-needed-xenial |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
|
| 2020-01-30 12:11:27 |
Łukasz Zemczak |
tags |
block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
|
| 2020-01-30 12:17:22 |
Łukasz Zemczak |
tags |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done-bionic verification-done-disco verification-done-xenial verification-needed verification-needed-eoan |
|
| 2020-01-30 16:58:37 |
Dan Streetman |
tags |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done-bionic verification-done-disco verification-done-xenial verification-needed verification-needed-eoan |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial verification-needed-eoan |
|
| 2020-01-30 16:58:51 |
Dan Streetman |
tags |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial verification-needed-eoan |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
|
| 2020-02-11 22:55:13 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-02-11 23:05:17 |
Launchpad Janitor |
network-manager (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-03-03 10:09:37 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-03-03 10:09:41 |
Łukasz Zemczak |
tags |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done-disco verification-done-eoan verification-done-xenial verification-needed verification-needed-bionic |
|
| 2020-03-04 15:01:54 |
Dan Streetman |
tags |
block-proposed-bionic block-proposed-disco block-proposed-xenial verification-done-disco verification-done-eoan verification-done-xenial verification-needed verification-needed-bionic |
block-proposed-disco block-proposed-xenial verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial |
|
| 2020-03-04 15:02:34 |
Dan Streetman |
network-manager (Ubuntu Disco): status |
Fix Committed |
Won't Fix |
|
| 2020-03-11 21:13:18 |
Launchpad Janitor |
network-manager (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-03-12 08:06:15 |
Marko Preuss |
bug |
|
|
added subscriber Marko Preuss |
| 2020-11-17 15:38:13 |
Dan Streetman |
network-manager (Ubuntu Xenial): assignee |
Dan Streetman (ddstreet) |
|
|
