Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
OCP Logging runs as a container and the latest currently supported version is based on RHEL 8 UBI and thus collects logs using `journalctl` from 8.6/8.7. systemd-journald in 9.2 cannot be configured to be compatible with journalctl from 8.6/8.7 without completely disabling compression.
Version-Release number of selected component (if applicable):
systemd-252
How reproducible:
100%
Steps to Reproduce:
1. Install RHEL 9.2
2. Run journalctl from within an 8.x container
3.
Actual results:
systemd-journald 252 cannot be configured to enable compatibility with 8.x journalctl without fully disabling compression which would significantly increase disk utilization and is undesirable.
Expected results:
systemd-journald 252 can be configured or defaults to LZ4 compression and can be configured such that 8.x journalctl can read the on disk format. We know that this will require the existing environment variables.
Environment="SYSTEMD_JOURNAL_COMPACT=0"
Environment="SYSTEMD_JOURNAL_KEYED_HASH=0"
Additional info:
We're requesting this as a transitional state, RHEL 9.3 and later can revert back to ZSTD being the only supported compression. By the time OCP uses 9.3 or later for RHCOS we expect all containers to have moved to UBI9.
(In reply to Colin Walters from comment #3)
> I typed this up, it compiles, haven't tested it:
This looks like the right way. And it should probably be done upstream, as it looks like an omission. I.e., we have env. vars to turn off other incompatible features, but none to force a particular compression algorithm.
(That said, I'm pretty sure the patch in its current form doesn't work. In particular, setting of .incompatible_flags in journal_file_init_header() needs to be updated too.)
> This looks like the right way. And it should probably be done upstream, as it looks like an omission. I.e., we have env. vars to turn off other incompatible features, but none to force a particular compression algorithm.
Right, agree. Would someone mind taking this ball and doing a PR upstream? I have to chase a different bug.
> (That said, I'm pretty sure the patch in its current form doesn't work. In particular, setting of .incompatible_flags in journal_file_init_header() needs to be updated too.)
Ah yes, indeed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6640