Sorry, I'm not understanding your comment.

What I understood is that the systemd developers said "It is not our
responsibility if ubuntu does not boot, this is not a systemd bug! In
fact, the issue in booting is caused by some quota related units,
shipped by Ubuntu, that are not part of systemd". Then, I saw that the
faulty systemd units are shipped with the "quota" package, just as you
say. Yet, the upstream quota package does not contain these units. The
systemd quota related units and scripts are a downstream ubuntu (maybe
from debian) addition (in fact, they live in the debian dir of the
package).

This is why I was reporting that the systemd developers suggest that
this is a downstream bug (a bug in the Ubuntu distro), not an upstream
bug (a bug in systemd 231).

I never implied that ubuntu forgot to ship some units. I'm only saying
that the quota units shipped with ubuntu evidently mistake something,
because when they are masked the system boots, otherwise it doesn't.

Possibly, the issue is only triggered if one has quotas+lvm2+fake or
soft raid. This may explain why the mistake got unnoticed when it
slipped in.

I suppose that this bug should be fixed by the maintainers of the quota
package in ubuntu, possibly with the help of the systemd maintainers.

** Package changed: systemd (Ubuntu) => quota (Ubuntu)

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

Title:
  Regression: quotas prevent yakkety from booting (boots once every ~4
  attempts)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1635023/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to