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 1232167 - Fails to "get", "print" the file and complete the file name using TAB when the file name has the special characters include "][|=()!,\ ".
Summary: Fails to "get", "print" the file and complete the file name using TAB when th...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: augeas
Version: 6.7
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Pino Toscano
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1186318
Blocks: 1232224 1301844
TreeView+ depends on / blocked
 
Reported: 2015-06-16 08:23 UTC by Hu Zhang
Modified: 2017-12-06 10:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1232224 (view as bug list)
Environment:
Last Closed: 2017-12-06 10:36:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Hu Zhang 2015-06-16 08:23:50 UTC 
Description of problem:
This bug is introduced by bug 1186318.
Fails to get, print the file and complete the file name using TAB key when file name has the special characters include "][|=()!,\ ".

Version-Release number of selected component (if applicable):
augeas-1.0.0-10.el6

How reproducible:
Always

Steps to Reproduce:
Step to reproduce:
1. Under /etc/sysconfig/network-scripts, create a file with the special characters include "][|=()!,\ ".
# ls /etc/sysconfig/network-scripts/ifcfg-weird*
/etc/sysconfig/network-scripts/ifcfg-weird\ [!]|=, (used to fail) 

Note: there is a whitespace at the end of the name.

2. Initialize the augtool and print the entries 
# augtool
augtool> print /files/etc/sysconfig/network-scripts/
/files/etc/sysconfig/network-scripts
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ 
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /DEVICE = "\"eth0\""
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /BOOTPROTO = "\"dhcp\""
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /HWADDR = "\"6C:AE:8B:20:80:82\""
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /IPV6INIT = "\"yes\""
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /MTU = "\"1500\""
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /NM_CONTROLLED = "\"yes\""
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /ONBOOT = "\"yes\""
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /TYPE = "\"Ethernet\""
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /UUID = "\"6d1866d3-83bf-473d-a934-190213c8ca11\""
...

augtool> match /files/etc/sysconfig/network-scripts/*
/files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\  = (none)
...

### So augtool can Initialize successfully.

3. Failed to use "tab" to auto complete the nodes in the file.
augtool> get /files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ 
### tap "tab" fails to get the nodes

4. When there are two similar files, "tab" fails to auto complete the file name.
# ls /etc/sysconfig/network-scripts/ifcfg-weird*
/etc/sysconfig/network-scripts/ifcfg-weird [!] (used to fail)
/etc/sysconfig/network-scripts/ifcfg-weird\ [!]|=, (used to fail)

augtool> ls /files/etc/sysconfig/network-scripts/ifcfg-weird\
### tap "tab" now
boot/  etc/   root/  usr/

It should display the two possible files instead these four directory. Seams that it happens when the taped file path taped includes the escape flag.


5. Fails to execute the print, ls, match or other commands when use the file directly.
augtool> print /files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ 
error: Failed to execute command
unknown escape sequence

augtool> get /files/etc/sysconfig/network-scripts/ifcfg-weird\\\ \[\!\]\|\=\,\ \(used\ to\ fail\)\ /DEVICE
error: Failed to execute command
unknown escape sequence



Actual results:
Described as above.

Expected results:
The scenarios in step 3, 4 and 5 should also be handled properly.

Additional info:
Comment 6 Jan Kurik 2017-12-06 10:36:33 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.