[Bug 1776891] Re: should disable journald rate limiting in live-server session

[Łukasz Zemczak]

Hello Michael, or anyone else affected,

Accepted livecd-rootfs into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.525.8 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed verification-failed-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  should disable journald rate limiting in live-server session

Status in subiquity:
  New
Status in livecd-rootfs package in Ubuntu:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  subiquity displays the curtin output by running curtin under systemd-cat. curtin can produce pretty large amounts of output and can hit journald rate limits, particularly when it fails (which is of course when you most want to see the output!). We should disable the rate limit in the installer.squashfs.

  [Test case]
  I guess make a CD with a deliberately broken subiquity that causes curtin to fail in a verbose way and ensure that all output is visible in subiquity's "view full log" screen.

  [Regression potential]
  Having no rate limit increases the chances of running the live system out of RAM if curtin is especially verbose I guess, but this would be an issue if we were spooling the log output to a file too.

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