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:
When /var/log is a dedicated file system, the logs that are generated while in "reboot phase" are lost because /var/log is not mounted in this phase, only / is mounted on /sysroot.
Having a dedicated /var/log is usual, typically for STIG compliant systems.
I understand it may be
Version-Release number of selected component (if applicable):
latest
How reproducible:
Always
Steps to Reproduce:
1. Upgrade a system having a dedicated /var/log
# leapp upgrade
2. Reboot to apply the upgrade
Actual results:
/var/log/leapp logs are pushed to "/sysroot/var/log/leapp" ("/sysroot" == "/" in the initramfs)
After upgrade, /var/log/leapp logs mounted from /var/log do not contain the "reboot" phase
Thank you Renaud for the report. I see the point. Regarding the description it seems that very same problem can be hit when /var is on separate partition. Maybe we need to reconsider mounting in the initramfs, or we could handle /var & /var/log in the same way as we do for /usr.
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 (leapp, leapp-repository, and cockpit-leapp 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-2020:4882
Description of problem: When /var/log is a dedicated file system, the logs that are generated while in "reboot phase" are lost because /var/log is not mounted in this phase, only / is mounted on /sysroot. Having a dedicated /var/log is usual, typically for STIG compliant systems. I understand it may be Version-Release number of selected component (if applicable): latest How reproducible: Always Steps to Reproduce: 1. Upgrade a system having a dedicated /var/log # leapp upgrade 2. Reboot to apply the upgrade Actual results: /var/log/leapp logs are pushed to "/sysroot/var/log/leapp" ("/sysroot" == "/" in the initramfs) After upgrade, /var/log/leapp logs mounted from /var/log do not contain the "reboot" phase