Bug 1554927

Summary: Fstab lens cannot parse lines with leading whitespaces [rhel-7.5.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: augeasAssignee: Pino Toscano <ptoscano>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact: Ioanna Gkioka <igkioka>
Priority: high    
Version: 7.5CC: igkioka, mtessun, ptoscano, rjones, yoguo
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: augeas-1.4.0-5.el7_5.1 Doc Type: Bug Fix
Doc Text:
Previously, Augeas was not able to parse lines in the /etc/fstab file if they had white spaces at the beginning. This update fixes the Fstab lens of Augeas to correctly ignore white spaces at the beginning of lines. As a result, Augeas now reads /etc/fstab as expected.
Story Points: ---
Clone Of: 1544520 Environment:
Last Closed: 2018-05-14 16:10:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1544520    
Bug Blocks:    

Description Oneata Mircea Teodor 2018-03-13 15:10:39 UTC
This bug has been copied from bug #1544520 and has been proposed to be backported to 7.5 z-stream (EUS).

Comment 3 YongkuiGuo 2018-03-29 10:34:52 UTC
Verified it with package:
augeas-1.4.0-5.el7_5.1.x86_64

Steps:
1. edit /etc/fstab and add whitespaces at the beginning of the following line:
  /dev/mapper/rhel_hp--dlxxx--04-home /home   xfs     defaults        0 0

2. run the augtool command:
augtool> print /files/etc/fstab
...
/files/etc/fstab/3
/files/etc/fstab/3/spec = "/dev/mapper/rhel_hp--dlxxx--04-home"
/files/etc/fstab/3/file = "/home"
/files/etc/fstab/3/vfstype = "xfs"
/files/etc/fstab/3/opt = "defaults"
/files/etc/fstab/3/dump = "0"
/files/etc/fstab/3/passno = "0"
...


So verified it.

Comment 6 errata-xmlrpc 2018-05-14 16:10:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1384