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.
Created attachment 1319207[details]
patch to add dot character to lexer pattern
Description of problem:
The lexer pattern for the options string does not accept the dot ('.') character, so setting an nfs v4 minor version with 'vers=4.0' fails as a syntax error.
(currently, only nfs4 version number is known to be affected; there may be others)
Version-Release number of selected component (if applicable):
autofs - all versions
How reproducible:
see below
Steps to Reproduce:
add a mount option in /etc/auto.master that includes a '.', for example:
/net -hosts vers=4.1
or
/mnt_indirect /etc/auto.indirect vers=4.1
Actual results:
# automount -m
.
syntax error while parsing map.
syntax error in map near [ bogus option ]
autofs dump map information
===========================
global options: none configured
...
Expected results:
mount option is valid syntax
# automount -m
autofs dump map information
===========================
global options: none configured
Mount point: /net
source(s):
type: hosts
map: vers=4.1
...
Additional info:
In some cases, vers=4,minorversion=1 can be used as a workaround
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:0977
Created attachment 1319207 [details] patch to add dot character to lexer pattern Description of problem: The lexer pattern for the options string does not accept the dot ('.') character, so setting an nfs v4 minor version with 'vers=4.0' fails as a syntax error. (currently, only nfs4 version number is known to be affected; there may be others) Version-Release number of selected component (if applicable): autofs - all versions How reproducible: see below Steps to Reproduce: add a mount option in /etc/auto.master that includes a '.', for example: /net -hosts vers=4.1 or /mnt_indirect /etc/auto.indirect vers=4.1 Actual results: # automount -m . syntax error while parsing map. syntax error in map near [ bogus option ] autofs dump map information =========================== global options: none configured ... Expected results: mount option is valid syntax # automount -m autofs dump map information =========================== global options: none configured Mount point: /net source(s): type: hosts map: vers=4.1 ... Additional info: In some cases, vers=4,minorversion=1 can be used as a workaround