[Bug 2109800] [NEW] systemd-fsckd functionality should be in plymouth directly

[Nick Rosbrook]

Public bug reported:

When systemd-fsckd was removed from upstream systemd, a small
helper/compatibility feature was left behind. When systemd-fsck is
running, it will connect to /run/systemd/fsck.progress, if it exists,
and point fsck to that fd for progress updates. The systemd-fsckd patch
in Ubuntu currently utilizes that, and then sends updates to plymouth.
This means that we currently have a situation like this:

 systemd-fsck at dev1.service -
 ...                        |-> systemd-fsckd.service -> plymouthd
 systemd-fsck at devN.service -

In other words, systemd-fsckd.service is a middleware. But, plymouthd
could simply listen on /run/systemd/fsck.progress itself.

There is already very similar logic for this in Ubuntu's plymouth via
debian/patches/ubuntu-spinner-fsck.patch. Instead of carrying the large
systemd-fsckd patch in systemd, we should consolidate the functionality
into the existing plymouth patches.

** Affects: plymouth (Ubuntu)
     Importance: Medium
     Assignee: Nick Rosbrook (enr0n)
         Status: New

** Affects: systemd (Ubuntu)
     Importance: Medium
     Assignee: Nick Rosbrook (enr0n)
         Status: Triaged

** Also affects: plymouth (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: plymouth (Ubuntu)
   Importance: Undecided => Medium

** Changed in: plymouth (Ubuntu)
     Assignee: (unassigned) => Nick Rosbrook (enr0n)

** Changed in: plymouth (Ubuntu)
     Assignee: Nick Rosbrook (enr0n) => (unassigned)

** Changed in: systemd (Ubuntu)
     Assignee: (unassigned) => Nick Rosbrook (enr0n)

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu)
       Status: New => Triaged

** Changed in: plymouth (Ubuntu)
     Assignee: (unassigned) => Nick Rosbrook (enr0n)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/2109800

Title:
  systemd-fsckd functionality should be in plymouth directly

Status in plymouth package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When systemd-fsckd was removed from upstream systemd, a small
  helper/compatibility feature was left behind. When systemd-fsck is
  running, it will connect to /run/systemd/fsck.progress, if it exists,
  and point fsck to that fd for progress updates. The systemd-fsckd patch
  in Ubuntu currently utilizes that, and then sends updates to plymouth.
  This means that we currently have a situation like this:

   systemd-fsck at dev1.service -
   ...                        |-> systemd-fsckd.service -> plymouthd
   systemd-fsck at devN.service -

  In other words, systemd-fsckd.service is a middleware. But, plymouthd
  could simply listen on /run/systemd/fsck.progress itself.

  There is already very similar logic for this in Ubuntu's plymouth via
  debian/patches/ubuntu-spinner-fsck.patch. Instead of carrying the
  large systemd-fsckd patch in systemd, we should consolidate the
  functionality into the existing plymouth patches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2109800/+subscriptions