The following issue was observed while running network-manager=1.8.4-1ubuntu3 autopkgtest on Artful:
-----------------------------------------------------------
Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating.
Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'.
-----------------------------------------------------------
This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem).
1. Issue
The following issue was observed while running network- manager= 1.8.4-1ubuntu3 autopkgtest on Artful:
------- ------- ------- ------- ------- ------- ------- ------- --- rfkill. service: Start operation timed out. Terminating. rfkill. service: Unit entered failed state. rfkill. service: Failed with result 'timeout'. ------- ------- ------- ------- ------- ------- ------- ---
Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-
Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-
-------
This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem).
2. How to reproduce
2.1. Download network-manager package source code
$ apt-get source network-manager
2.2. Run killswitches- no-urfkill testcase manager- 1.8.4 tests/killswitc hes-no- urfkill
$ cd network-
$ sudo ./debian/
3. Fix
The issue is fixed by the following systemd upstream patches:
------- ------- ------- ------- ------- ------- ------- ------- --- /github. com/systemd/ systemd/ commit/ 8ec1a07998758f6 a85f3ea5bf2ed14 d87609398f# diff-2759479676 77827e2b72930d9 7f1b8ac
https:/
commit 8ec1a07998758f6 a85f3ea5bf2ed14 d87609398f
Author: S. Fan <email address hidden>
Date: Mon Jul 31 05:10:10 2017 -0500
rfkill: fix erroneous behavior when polling the udev monitor (#6489)
Comparing udev_device_ get_sysname( device) and sysname will always return
true. We need to check the device received from udev monitor instead.
Also, fd_wait_for_event() sometimes never exits. Better set a timeout ------- ------- ------- ------- ------- ------- ------- ---
here.
-------
------- ------- ------- ------- ------- ------- ------- ------- --- /github. com/systemd/ systemd/ commit/ c7f6ca9379279af fa8f22d15fa1306 3491f86a49# diff-2759479676 77827e2b72930d9 7f1b8ac
https:/
commit c7f6ca9379279af fa8f22d15fa1306 3491f86a49
Author: Xiang Fan <email address hidden>
Date: Wed Aug 9 05:51:53 2017 -0500
rfkill: fix typo (#6574) ------- ------- ------- ------- ------- ------- ------- ---
-------
With the fixed, the output from systemd-rfkill is:
------- ------- ------- ------- ------- ------- ------- ------- --- rfkill[ 14843]: Timed out waiting for udev monitor. ------- ------- ------- ------- ------- ------- ------- ---
Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 28 15:27:59 autopkgtest systemd-
Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status.
-------
The patches are needed to fix the ADT tests observed with Artful tests on ppc64el architecture: /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- artful/ artful/ ppc64el/ n/network- manager/ 20171120_ 100719_ 28642@/ log.gz
https:/