Description of problem: In %post section we are already in chrooted environment. So --log /mnt/sysimage/root/install.post.log will create log file with this path in the actual OS file structure. It should be directing logs to /root/install.post.log as we did prior. Version-Release number of selected component (if applicable): Satelliet 6.6 How reproducible: Always Steps to Reproduce: 1. Provision a system with satellite 6 2. Post logs are in /mnt/sysimage/root/install.post.log instead of /root/install.post.log Expected results: provisioning template should not hould not be creating logging files under /mnt Additional info:
Upstream bug assigned to lzap
Just to add another data point, I was able to duplicate this in my lab very easily. I am using Sat 6.6 and standard kickstart templates, and PXE provisioned a normal RHEL 7.7 guest and this is the results after the machine was provisioned: https://share.getcloudapp.com/RBudj5r2 Adding myself to this BZ as well so I can keep a customer updated on its status. I'm happy to help test in my lab.
It appears that this file is severely limited in terms of its usefulness when compared to previous information stored within this file. From what I'm seeing, it's missing the majority of its previous contents such as Subscription Manager registration and other snippet output (Katello agent package install information, etc) and yum update logging information. Easily, less than perhaps a tenth of the typical information as previously seen is contained within this log file now. With this said, there is a bigger issue than this log file simply not being placed in root's home directory. This lack of log detail was noticed on a recent RHEL 8.1 and 7.7 server.
Hello, some of the logging is now redirected into /root/install.postnochroot.log - check that file.
WORKAROUND: Use the following template change: https://gitlab.sat.engineering.redhat.com/satellite6/foreman/-/merge_requests/520/diffs
Hello, any version. It is one line change.
VERIFIED on sat6.8.0-16 the install.post.log is correctly placed inside /root/ directory now.
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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366