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.

Cannot get kickstart file containing process substitution in %post
to work correctly.  Explicitly setting interpreter (--interpreter)
to /bin/bash won't help.

Either I am missing something or this is a bug.

Found /tmp/ks-script-wauWIy (standalone %post section) and the respective
/tmp/ks-script-wauWIy.log states:

> cat: /dev/fd/63: No such file or directory
> cat: /dev/fd/62: No such file or directory
> tail: write error: Broken pipe

(where tail is one of the two commands used for process substitutions)

Looks like the chroot environment is not built properly incl. /dev
hierarchy (if possible, indeed, not a chroot expert), effectively
preventing process substitution?  If it's a known limitation, it doesn't
seem to be properly documented.  Definitely more desired would be to
prevent any such artificial and unobvious limitations
(process substitution is a standard feature of bash).

Oh, [bug 814850].

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