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.

Bug 1431068

Summary: zsh causes "name:#: parse error" after updating to zsh-5.0.2-25.el7_3.1.x86_64
Product: Red Hat Enterprise Linux 7 Reporter: dbodnarc
Component: zshAssignee: Kamil Dudka <kdudka>
Status: CLOSED CANTFIX QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: kdudka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-30 07:40:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description dbodnarc 2017-03-10 09:45:35 UTC 
Description of problem:
`zsh` behavior changed after the following bugfix:
Bug 1399534 - zsh heredoc crash (zsh-5.0.2-25.el7_3.1)

Version-Release number of selected component (if applicable):
zsh-5.0.2-25.el7_3.1

How reproducible:
After updating of `zsh` package it started to fail with "name:#: parse error" caused by `BLDARC` followed by other character(s).

Steps to Reproduce:
Customer installed the updated package and got the following error - 'parse error':
---------------------------------------------------
[root@fastvm-r7-3-73 ~]# rpm -q zsh
zsh-5.0.2-25.el7_3.1.x86_64
[root@fastvm-r7-3-73 ~]# cat -n try2
     1	cat >> /tmp/try <<EOF
     2	# Begin code generated from ${script} -----
     3	export A="$(tr '\n' ' ' <<BLDARC
     4	content
     5	BLDARC)"
     6	EOF
[root@fastvm-r7-3-73 ~]# zsh try2
try2:7: parse error
---------------------------------------------------

but script was working on (zsh-5.0.2-7.el7.x86_64):
--------------------------------------------------
[root@fastvm-r7-3-73 ~]# rpm -q zsh
zsh-5.0.2-7.el7.x86_64
[root@fastvm-r7-3-73 ~]# cat -n try2
     1	cat >> /tmp/try <<EOF
     2	# Begin code generated from ${script} -----
     3	export A="$(tr '\n' ' ' <<BLDARC
     4	content
     5	BLDARC)"
     6	EOF
[root@fastvm-r7-3-73 ~]# zsh try2
[root@fastvm-r7-3-73 ~]# cat /tmp/try 
# Begin code generated from  -----
export A="content "
---------------------------------------------------


Actual results:
> try2:7: parse error

Expected results:
> executed successfully


Additional info:
BZ# References:
Bug 1399534 - zsh heredoc crash (7.3.z : ERRATA CLOSED)
Bug 1374752 - zsh heredoc crash (7.4.0 : ... )
Comment 2 Kamil Dudka 2017-03-13 18:52:25 UTC 
Thank you for reporting the change in behavior!

Unfortunately, there is not much we can do about it.  Upstream says this is the expected (and already documented) behavior of zsh:

http://www.zsh.org/mla/workers/2016/msg01764.html

The script needs to be fixed to comply with the documented behavior of zsh by inserting a newline character between BLDARC and )".

The change in behavior was introduced by the fix for bug #1374752, which fixes a regression introduced by the fix for bug #1241023.  I am not aware of any safe way to reintroduce the (undocumented) behavior of here-documented that used to be available before fixing #1241023.
Comment 3 Kamil Dudka 2017-06-30 07:40:15 UTC 
Per comment #2 closing CANTFIX.