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.

Created attachment 918510 [details]
kickstart file with %post script

Description of problem:
During a kickstart %post script (without --nochroot option) a log file is created in the non-chrooted filesystem that is empty even if the script produces output.  

Version-Release number of selected component (if applicable): rhel7GA


How reproducible: always


Steps to Reproduce:
1. start kickstart installation with a %post script that produces output
2. cat logfile in /tmp corresponding to post script in /mnt/sysimage/tmp


Actual results:
Empty log file

Expected results:
Log file containing output of %post script

Additional info:

Check /var/log/anaconda/ on the target system. Is it there?

Once installation is complete the post script logs show up in /var/log/anaconda/ on the target system.  While the scripts are running there is no corresponding log file on the target system.  The ks-script-xxx log in /tmp also remains empty while the scripts are running.

That is as expected, because of buffering the output may not be written to the files immediately.

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.