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:
/var/log/journal should not be reported by rpm -V as an error
If the /var/log/journal directory is created, systemd will set the group on this directory to systemd-journal.  The spec file does not set a group on this directory so the default value causes the verification to fail.

Version-Release number of selected component (if applicable):
systemd-219-57.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. [[ ! -d /var/log/journal ]] && mkdir -p /var/log/journal
2. reboot
3. rpm -V systemd

Actual results:
# rpm -V systemd
.M....G..  g /var/log/journal

Expected results:
No error

Additional info:

In theory, we could use something like "%verify(not md5)" in the spec file, but it doesn't really matter and doesn't make much sense for a ghosted file. And since you created the directory yourself, you should also set the right permissions yourself. IMO, this is nothing to fix.

I actually can't set a permanent correct group on the directory.  That's the bug.  I can change the group on /var/log/journal to root, and it will verify correctly.  But once I reboot the system, systemd will set the group on /var/log/journal back to systemd-journal and once again fail to verify.

The spec file states in a comment in %post that the journal files *will* be owned by the systemd-journal group, but verify is checking for root.  The spec file doesn't need a %verify(not md5), it needs something like %attr(-, -, systemd-journal) to be consistent with how systemd works.

*** This bug has been marked as a duplicate of bug 1545372 ***