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@lists.fedoraproject.org/…https://fedoraproject.org/wiki/Basic_Release_Criteria#System_logging
--
Chris Murphy
Good day Thomas,
I'm working on Anaconda (Fedora/RHEL/CentOS installer) and we have
recently seen your presentation about addon on Anaconda you are using
for the CERN purposes[0]. That's great to hear you are using and
extending our project. Hope you like how Anaconda progress.
I want to ask you about current status of this addon. If you are using
it or testing it on Fedora or if you are planning to adapt it on RHEL-
8? The reason is that we are doing a bigger improvement of how Anaconda
is working on the backend side and it will probably touch your addon.
We want to provide you a stable API which you and even us will use. You
can look on my presentation [1] and our blog [2] unfortunately
it's little bit outdated but the main idea stays the same. You can also
look on the recent upstream changes, all the work we are doing is more
or less used on Fedora even now.
I writing you mainly because we want to avoid breaking of your addon.
In case you will have problems with the addon thanks to the transition
to a new solution please feel free to contact us on
mailing list:
anaconda-devel-list(a)redhat.com
or IRC:
freenode #anaconda
[0]:
https://www.youtube.com/watch?v=Fbml_WGMnoQ&feature=youtu.be&list=PLuRtbOXp…
[1]: https://www.youtube.com/watch?v=00W8SsRrU8g&t=1s
[2]:
https://rhinstaller.wordpress.com/2017/10/09/anaconda-modularisation/https://rhinstaller.wordpress.com/2017/11/23/anaconda-modularization-instal…
Best regards,
Jirka