This bug was fixed in the package systemd - 239-7ubuntu10.14
---------------
systemd (239-7ubuntu10.14) cosmic; urgency=medium
* d/p/resolved-rework-how-we-determine-which-scope-to-send.patch
- fix DNS leakage (LP: 1754671)
* d/t/boot-and-services:
- skip test_no_failed if gdm failed to start (LP: #1830484)
* d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)
* d/t/boot-smoke:
- Fix false negative checking for running jobs after boot
(LP: #1825997)
-- Dan Streetman <ddstr...@canonical.com> Wed, 24 Apr 2019 17:08:26
-0400
** Changed in: systemd (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1830484
Title:
boot-and-services test_no_failed fails if gdm failed to start in
testbed
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Cosmic:
Fix Released
Bug description:
[impact]
gdm on cosmic running in the autopkgtest is flaky and sometimes fails
to start; when it does it causes other systemd service failures like
'user@118.service' or other services, which fail the test case.
the test_gdm3 testcase was already skipped because of this in bug
1790478, the test_no_failed testcase needs to be skipped as well if
gdm fails to start.
[test case]
the failure is intermittent, but looking through old cosmic systemd
autopkgtest logs look for:
May 23 11:13:38 autopkgtest systemd[1]: user@118.service: Killing process
1251 (systemctl) with signal SIGKILL.
May 23 11:13:38 autopkgtest systemd[1]: Stopped User Manager for UID 118.
May 23 11:13:39 autopkgtest systemd[1]: Starting User Manager for UID 118...
May 23 11:13:37 autopkgtest systemd[1280]: pam_unix(systemd-user:session):
session opened for user gdm by (uid=0)
May 23 11:13:38 autopkgtest systemd[1280]: Failed to fully start up daemon:
Permission denied
May 23 11:13:38 autopkgtest systemd[1]: user@118.service: Failed with result
'protocol'.
May 23 11:13:38 autopkgtest systemd[1]: Failed to start User Manager for UID
118.
FAIL
test_rsyslog (__main__.ServicesTest) ... ok
test_tmp_cleanup (__main__.ServicesTest) ... ok
test_tmp_mount (__main__.ServicesTest) ... ok
test_udev (__main__.ServicesTest) ... ok
======================================================================
FAIL: test_no_failed (__main__.ServicesTest)
No failed units
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/tmp/autopkgtest.jGFP4N/build.FWq/src/debian/tests/boot-and-services", line
62, in test_no_failed
self.assertEqual(failed, [])
AssertionError: Lists differ: ['user@118.service loaded failed failed User
Manager for UID 118'] != []
First list contains 1 additional elements.
First extra element 0:
'user@118.service loaded failed failed User Manager for UID 118'
- ['user@118.service loaded failed failed User Manager for UID 118']
+ []
[regression potential]
low; testcase skipping due to flaky gdm inside autopkgtest, only on
cosmic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830484/+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
