should disable journald rate limiting in live-server session
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
Fix Released
|
Undecided
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
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.
Related branches
- Steve Langasek: Approve
-
Diff: 34 lines (+10/-0) (has conflicts)2 files modifieddebian/changelog (+9/-0)
live-build/ubuntu-server/includes.binary/overlay/etc/systemd/journald.conf.d/no-rate-limit.conf (+1/-0)
- Steve Langasek: Approve
-
Diff: 24 lines (+6/-0)2 files modifieddebian/changelog (+5/-0)
live-build/ubuntu-server/includes.binary/overlay/etc/systemd/journald.conf.d/no-rate-limit.conf (+1/-0)
tags: | added: id-5b224cde9b772a957099c27e |
Changed in subiquity: | |
status: | New → Fix Released |
Changed in livecd-rootfs (Ubuntu): | |
status: | In Progress → Fix Released |
We didn't land this still?