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, deleting it, causing the loss of early boot and startup messages. Why I think Anaconda team might care: LiveOS is inherently a non-deterministic environment for the installer, and losing a bunch of early boot and startup messages like all the liveos assembly, the overlay (whether dm or overlayfs based in the future), networking, udev and other non-kernel device discovery, and dracut debug messages - don't exist in the journal and quite a lot of such messages for whatever reason do not forward to console or kmsg when using systemd.journald.forward_to_X parameters. Therefore if the journal is deleted, the messages are flat out gone and any troubleshooting and introspection is really difficult. 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. So there is a proposal over on test@ list to change the location of this requirement so that it applies to installer images. And I figured installer devs might have an opinion if this is blocker worthy. https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx/message/QAV3I2W6337ZW7CSYJYAU2SY3GL4KI6F/ https://fedoraproject.org/wiki/Basic_Release_Criteria#System_logging -- Chris Murphy _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
