Public bug reported: [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 ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Groovy) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Groovy) Status: New => In Progress ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Description changed: [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, and this is just a - backport of that fix to 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 -- 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/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: In Progress 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 -- 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
