| 2017-11-20 12:39:35 |
Kleber Sacilotto de Souza |
bug |
|
|
added bug |
| 2017-11-20 12:39:44 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Artful |
|
| 2017-11-20 13:00:05 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2017-11-20 13:00:06 |
Ubuntu Kernel Bot |
tags |
|
artful |
|
| 2017-11-20 15:38:12 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Artful) |
|
| 2017-11-20 15:38:18 |
Joseph Salisbury |
linux (Ubuntu Artful): status |
New |
Triaged |
|
| 2017-11-20 15:38:21 |
Joseph Salisbury |
linux (Ubuntu): status |
Incomplete |
Triaged |
|
| 2017-11-20 15:38:24 |
Joseph Salisbury |
linux (Ubuntu Artful): importance |
Undecided |
Medium |
|
| 2017-11-20 15:38:26 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-11-20 19:42:25 |
Joseph Salisbury |
tags |
artful |
artful kernel-key |
|
| 2017-11-29 09:42:46 |
Kleber Sacilotto de Souza |
bug task added |
|
network-manager (Ubuntu) |
|
| 2017-11-29 16:55:39 |
Kleber Sacilotto de Souza |
attachment added |
|
1-1.8.4-1ubuntu4.debdiff https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+attachment/5016266/+files/1-1.8.4-1ubuntu4.debdiff |
|
| 2017-11-29 16:56:56 |
Kleber Sacilotto de Souza |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2017-11-29 17:18:53 |
Kleber Sacilotto de Souza |
description |
ppc64el ADT log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz
Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----
Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18 |
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz
Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----
Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18
[Test Case]
2.1. Download network-manager package source code
$ apt-get source network-manager
2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill
[Regression Potential]
No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout.
[Other Info]
On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. |
|
| 2017-12-02 07:11:59 |
Mathew Hodson |
bug |
|
|
added subscriber Mathew Hodson |
| 2017-12-04 15:11:40 |
Joseph Salisbury |
tags |
artful kernel-key |
artful |
|
| 2018-03-05 07:00:06 |
Mathew Hodson |
network-manager (Ubuntu): importance |
Undecided |
Medium |
|
| 2018-03-05 07:00:09 |
Mathew Hodson |
network-manager (Ubuntu Artful): importance |
Undecided |
Medium |
|
| 2018-03-05 07:01:24 |
Mathew Hodson |
bug task deleted |
linux (Ubuntu Artful) |
|
|
| 2018-03-05 07:01:30 |
Mathew Hodson |
bug task deleted |
linux (Ubuntu) |
|
|
| 2018-08-17 04:40:38 |
Simon Quigley |
network-manager (Ubuntu Artful): status |
New |
Won't Fix |
|
| 2018-08-17 04:41:15 |
Simon Quigley |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2019-12-09 14:43:13 |
Dan Streetman |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-12-09 14:43:13 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Eoan) |
|
| 2019-12-09 14:43:13 |
Dan Streetman |
nominated for series |
|
Ubuntu Focal |
|
| 2019-12-09 14:43:13 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Focal) |
|
| 2019-12-09 14:43:13 |
Dan Streetman |
nominated for series |
|
Ubuntu Disco |
|
| 2019-12-09 14:43:13 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Disco) |
|
| 2019-12-09 14:50:53 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2019-12-09 14:50:57 |
Dan Streetman |
network-manager (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2019-12-09 14:50:59 |
Dan Streetman |
network-manager (Ubuntu Disco): importance |
Undecided |
Medium |
|
| 2019-12-10 14:45:26 |
Martin Wimpress |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2019-12-11 02:02:59 |
Mathew Hodson |
removed subscriber Mathew Hodson |
|
|
|
| 2019-12-11 02:04:50 |
Mathew Hodson |
tags |
artful |
artful testcase |
|
| 2020-01-08 21:38:15 |
Dan Streetman |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2020-03-24 14:38:45 |
Sebastien Bacher |
network-manager (Ubuntu Disco): status |
New |
Won't Fix |
|
| 2020-03-25 19:03:33 |
Dan Streetman |
bug |
|
|
added subscriber Dariusz Gadomski |
| 2020-03-25 21:16:06 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2020-03-30 17:48:14 |
Dan Streetman |
tags |
artful testcase |
artful sts-sponsor-volunteer testcase |
|
| 2020-03-30 18:04:07 |
Dariusz Gadomski |
network-manager (Ubuntu Eoan): assignee |
|
Dariusz Gadomski (dgadomski) |
|
| 2020-03-30 18:04:09 |
Dariusz Gadomski |
network-manager (Ubuntu Focal): assignee |
|
Dariusz Gadomski (dgadomski) |
|
| 2020-03-30 19:06:38 |
Dariusz Gadomski |
network-manager (Ubuntu Eoan): assignee |
Dariusz Gadomski (dgadomski) |
|
|
| 2020-03-30 19:06:39 |
Dariusz Gadomski |
network-manager (Ubuntu Focal): assignee |
Dariusz Gadomski (dgadomski) |
|
|
| 2020-04-07 06:35:47 |
Seyeong Kim |
bug |
|
|
added subscriber Seyeong Kim |
| 2020-04-07 13:44:51 |
Martin Wimpress |
network-manager (Ubuntu Eoan): status |
New |
Won't Fix |
|
| 2020-04-07 13:45:13 |
Martin Wimpress |
tags |
artful sts-sponsor-volunteer testcase |
sts-sponsor-volunteer testcase |
|
| 2020-04-07 14:25:07 |
Dan Streetman |
network-manager (Ubuntu Focal): assignee |
|
Seyeong Kim (xtrusia) |
|
| 2020-04-21 05:27:05 |
Seyeong Kim |
description |
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz
Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----
Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18
[Test Case]
2.1. Download network-manager package source code
$ apt-get source network-manager
2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill
[Regression Potential]
No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout.
[Other Info]
On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. |
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz
Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----
Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18
[Test Case]
Assume that test vm and host are ppc64
1. deploy ppc64 vm instance ( with 1 cpu )
2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
3. apt install network-manager rfkill
4. modify /etc/netplan/[conf], renderer as NetworkManager
5. netplan apply
6. run below command
- nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi
enabled
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
enabled
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
enabled
second 'enabled' should be 'disabled' but not updated properly.
[Regression Potential]
No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout.
[Other Info]
On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful.
# original test case
2.1. Download network-manager package source code
$ apt-get source network-manager
2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill |
|
| 2020-04-23 07:36:02 |
Seyeong Kim |
description |
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz
Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----
Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18
[Test Case]
Assume that test vm and host are ppc64
1. deploy ppc64 vm instance ( with 1 cpu )
2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
3. apt install network-manager rfkill
4. modify /etc/netplan/[conf], renderer as NetworkManager
5. netplan apply
6. run below command
- nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi
enabled
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
enabled
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
enabled
second 'enabled' should be 'disabled' but not updated properly.
[Regression Potential]
No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout.
[Other Info]
On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful.
# original test case
2.1. Download network-manager package source code
$ apt-get source network-manager
2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill |
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz
Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----
Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18
[Test Case]
Assume that test vm and host are ppc64
1. deploy ppc64 vm instance ( with 1 cpu )
2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
3. apt install network-manager rfkill
4. modify /etc/netplan/[conf], renderer as NetworkManager
5. netplan apply
6. run below command
- nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi
enabled
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
enabled
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
enabled
second 'enabled' should be 'disabled' but not updated properly.
Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock.
[Regression Potential]
No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout.
[Other Info]
On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful.
# original test case
2.1. Download network-manager package source code
$ apt-get source network-manager
2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill |
|
| 2020-04-24 17:09:35 |
Dan Streetman |
description |
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz
Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----
Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18
[Test Case]
Assume that test vm and host are ppc64
1. deploy ppc64 vm instance ( with 1 cpu )
2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
3. apt install network-manager rfkill
4. modify /etc/netplan/[conf], renderer as NetworkManager
5. netplan apply
6. run below command
- nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi
enabled
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
enabled
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
enabled
second 'enabled' should be 'disabled' but not updated properly.
Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock.
[Regression Potential]
No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout.
[Other Info]
On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful.
# original test case
2.1. Download network-manager package source code
$ apt-get source network-manager
2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill |
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock.
ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz
Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----
Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18
[Test Case]
Assume that test vm and host are ppc64
1. deploy ppc64 vm instance ( with 1 cpu )
2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
3. apt install network-manager rfkill
4. modify /etc/netplan/[conf], renderer as NetworkManager
5. netplan apply
6. run below command
- nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi
enabled
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
enabled
0: fake: Wireless LAN
Soft blocked: yes
Hard blocked: no
0: fake: Wireless LAN
Soft blocked: no
Hard blocked: no
enabled
second 'enabled' should be 'disabled' but not updated properly.
Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock.
[Regression Potential]
This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs.
[scope]
this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix.
[Other Info]
this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network-manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail.
There are (at least) 2 options to fix this:
1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status
This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme).
[original description]
On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful.
# original test case
2.1. Download network-manager package source code
$ apt-get source network-manager
2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill |
|
| 2020-04-24 17:09:42 |
Dan Streetman |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-04-24 17:09:42 |
Dan Streetman |
bug task added |
|
network-manager (Ubuntu Bionic) |
|
| 2020-04-24 17:40:42 |
Dan Streetman |
tags |
sts-sponsor-volunteer testcase |
block-proposed-bionic block-proposed-eoan block-proposed-focal sts-sponsor-volunteer testcase |
|
| 2020-04-24 17:40:52 |
Dan Streetman |
network-manager (Ubuntu Eoan): status |
Won't Fix |
In Progress |
|
| 2020-04-24 17:40:55 |
Dan Streetman |
network-manager (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-04-24 17:40:57 |
Dan Streetman |
network-manager (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-04-24 17:41:06 |
Dan Streetman |
network-manager (Ubuntu Bionic): assignee |
|
Seyeong Kim (xtrusia) |
|
| 2020-04-24 17:41:14 |
Dan Streetman |
network-manager (Ubuntu Eoan): assignee |
|
Seyeong Kim (xtrusia) |
|
| 2020-04-28 23:12:21 |
Brian Murray |
network-manager (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-04-28 23:12:24 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-04-28 23:12:27 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2020-04-28 23:12:32 |
Brian Murray |
tags |
block-proposed-bionic block-proposed-eoan block-proposed-focal sts-sponsor-volunteer testcase |
block-proposed-bionic block-proposed-eoan block-proposed-focal sts-sponsor-volunteer testcase verification-needed verification-needed-focal |
|
| 2020-04-28 23:14:36 |
Brian Murray |
network-manager (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2020-04-28 23:14:45 |
Brian Murray |
tags |
block-proposed-bionic block-proposed-eoan block-proposed-focal sts-sponsor-volunteer testcase verification-needed verification-needed-focal |
block-proposed-bionic block-proposed-eoan block-proposed-focal sts-sponsor-volunteer testcase verification-needed verification-needed-eoan verification-needed-focal |
|
| 2020-04-28 23:26:29 |
Brian Murray |
network-manager (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-04-28 23:26:37 |
Brian Murray |
tags |
block-proposed-bionic block-proposed-eoan block-proposed-focal sts-sponsor-volunteer testcase verification-needed verification-needed-eoan verification-needed-focal |
block-proposed-bionic block-proposed-eoan block-proposed-focal sts-sponsor-volunteer testcase verification-needed verification-needed-bionic verification-needed-eoan verification-needed-focal |
|
| 2020-04-29 00:14:56 |
Mathew Hodson |
network-manager (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2020-05-02 04:49:05 |
Launchpad Janitor |
network-manager (Ubuntu): status |
New |
Fix Released |
|
| 2020-05-05 18:49:20 |
Dan Streetman |
tags |
block-proposed-bionic block-proposed-eoan block-proposed-focal sts-sponsor-volunteer testcase verification-needed verification-needed-bionic verification-needed-eoan verification-needed-focal |
block-proposed-bionic block-proposed-eoan block-proposed-focal testcase verification-done verification-done-bionic verification-done-eoan verification-done-focal |
|
| 2020-06-02 06:21:06 |
Sebastien Bacher |
tags |
block-proposed-bionic block-proposed-eoan block-proposed-focal testcase verification-done verification-done-bionic verification-done-eoan verification-done-focal |
block-proposed-bionic block-proposed-eoan testcase verification-done verification-done-bionic verification-done-eoan verification-done-focal |
|
| 2020-08-18 15:24:27 |
Launchpad Janitor |
network-manager (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-08-18 15:24:30 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-12-11 07:33:55 |
Mathew Hodson |
tags |
block-proposed-bionic block-proposed-eoan testcase verification-done verification-done-bionic verification-done-eoan verification-done-focal |
block-proposed-bionic testcase verification-done verification-done-bionic verification-done-eoan verification-done-focal |
|
| 2023-06-01 08:02:46 |
Łukasz Zemczak |
network-manager (Ubuntu Bionic): status |
Fix Committed |
Won't Fix |
|
| 2023-06-05 11:32:44 |
Dan Streetman |
removed subscriber Dan Streetman |
|
|
|
