release criterion change proposal related to system logging on LiveOS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Summary: On Fedora LiveOS, e.g.
Fedora-Workstation-Live-x86_64-Rawhide-20190728.n.1.iso, the journal
is missing the first 20-30s of all boot/startup related messages. The
reason is a bit complicated, systemd-journald appears to have a bug
wanting keep_free space too high, and Fedora's lives have had
shrinking free space consistently over time as the "payload" gets
bigger. The result is now systemd-journald almost immediately vacuums
the first journal file during startup of the Live image, deleting it
and causing the loss of early boot and startup messages.

I proposed this as a blocker bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1715699

It's been rejected twice, mainly because the Fedora Basic Release
Criterion for system logging applies to the post-installed system. It
doesn't apply to any of the installer images. There is a proposal over
on test@ list to change the location of this requirement so that it
applies to installer images also. I figured some developers might
care, in particular if they have early startup services: dracut,
networking, device discovery, udev. No one disputes it's a nasty bug
and should be fixed. The question is whether missing early boot
messages is bad enough bug to block the release until it gets fixed.

https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx/message/QAV3I2W6337ZW7CSYJYAU2SY3GL4KI6F/

https://fedoraproject.org/wiki/Basic_Release_Criteria#System_logging


As an example of how pernicious it is, this bug actually started with
Fedora 30, but wasn't triggered out of the box with default boot
options. But if you needed more debugging in the logs, rd.debug or
rd.udev.debug or systemd.log_level=debug, or most any system service
set to debug mode, would cause the journal file to become bigger
faster, triggering the bug, and causing all of that early startup
messages in the log to be deleted. So, that bug is now permanently
baked into Fedora 30 media, and there's no way to do any serious early
boot debugging - that data is simply gone.


-- 
Chris Murphy
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux