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:
anaconda adds a '?' at the end of post commands
How reproducible:
100%
Steps to Reproduce:
%post
touch /root/whatever
%end
Actual results:
/root/whatever?
Expected results:
/root/whatever
Additional info:
Easy workaround is to end each line with '#', but if you aren't expecting it you get really weird behaviour.
Can you attach the logs from the installation (in /tmp/ before the install environment is rebooted, copied to /var/log/anaconda/ in the installed system), and the kickstart you are using with any passwords or other private data removed? Is the character being added a question mark (0x3F) or some other non-printable character, like a carriage return from msdos line endings (0x0D)?
$ file freshexam.ks.cfg
freshexam.ks.cfg: ASCII text, with CRLF line terminators
Convert the file to use Unix line endings. The dos2unix utility can do this for you.