[Bug 1908067] Re: systemd-fsckd test fails on groovy checking plymouth-start isactive
Dan Streetman
1908067 at bugs.launchpad.net
Wed Jan 13 19:02:10 UTC 2021
autopkgtest passes on groovy:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/s/systemd/20210112_092742_83d2c@/log.gz
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1908067
Title:
systemd-fsckd test fails on groovy checking plymouth-start isactive
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Groovy:
Fix Committed
Bug description:
[impact]
systemd-fsckd test fails on groovy because plymouth-start service is
active
[test case]
check autopkgtest logs of systemd-fsckd test case on groovy
[regression potential]
incorrectly passed, or failed, systemd-fsckd test
[scope]
this is needed only for groovy.
the plymouth-start.service did not include RemainAfterExit=true before groovy, so the service is expected to be inactive when checked by the test before groovy. this is already fixed in hirsute:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c46eda821e97df5595a4cdc5f5c41a9b49a51745
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908067/+subscriptions
More information about the foundations-bugs
mailing list