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 1184584

Summary: autofs: validate_location: invalid character " " found in location
Product: Red Hat Enterprise Linux 7 Reporter: Francisco Javier Lopez Y Grueber <flg>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED NOTABUG QA Contact: Filesystem QE <fs-qe>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.0   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-27 01:30:53 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 Francisco Javier Lopez Y Grueber 2015-01-21 17:49:46 UTC
Description of problem:

automount complains about invalid character in locations

Version-Release number of selected component (if applicable):

7.0

How reproducible:

ALWAYS

Steps to Reproduce:
1. On IDM Server Session 1:

systemctl autofs stop 
autofs -d -f

Session 2 on IDM 

Try to login as user and have the userdir created on the share 

su - flg 

2.
Session 1 OUTPUT: 

lookup_nss_read_map: reading map sss auto.home2
parse_init: parse(sun): init gathered global options: (null)
lookup_read_map: map read not needed, so not done
lookup_nss_read_map: reading map files auto.home2
file map /etc/auto.home2 not found
st_ready: st_ready(): state = 4 path /home/nfs
handle_packet: type = 3
handle_packet_missing_indirect: token 129, name mv, request pid 14994
attempting to mount entry /home/nfs/mv
lookup_mount: lookup(sss): looking up mv
lookup_mount: lookup(sss): flg -> rw,soft 192.168.55.1:/nfsexport/home/&
parse_mount: parse(sun): expanded entry: rw,soft 192.168.55.1:/nfsexport/home/flg
parse_mount: parse(sun): gathered options: 
validate_location: invalid character " " found in location rw,soft 192.168.55.1:/nfsexport/home/flg
lookup_name_file_source_instance: file map not found
dev_ioctl_send_fail: token = 129
failed to mount /home/nfs/flg
handle_packet: type = 3
handle_packet_missing_indirect: token 130, name mv, request pid 14994
dev_ioctl_send_fail: token = 130
handle_packet: type = 3
handle_packet_missing_indirect: token 131, name mv, request pid 14994
dev_ioctl_send_fail: token = 131
handle_packet: type = 3
handle_packet_missing_indirect: token 132, name mv, request pid 14994
dev_ioctl_send_fail: token = 132
handle_packet: type = 3
handle_packet_missing_indirect: token 133, name mv, request pid 14994


Actual results:

The automount complains about invalid character. 

Expected results:

Mount succeeds -> Directory will be created. 


Additional info:

Found a Bug with similar problem related to the % expansion. 
 
https://bugzilla.redhat.com/show_bug.cgi?id=1036032

The complained " " guided to search for an empty space within the configuration file. Which, was not the case.

Comment 2 Ian Kent 2015-01-22 01:49:41 UTC
I'll have a go at reproducing this and see what I can find.

Comment 3 Ian Kent 2015-01-22 02:18:19 UTC
(In reply to Francisco Javier Lopez Y Grueber from comment #0)
> Description of problem:
> 
> automount complains about invalid character in locations

snip ...

> Try to login as user and have the userdir created on the share 
> 
> su - flg 
> 
> 2.
> Session 1 OUTPUT: 
> 
> lookup_nss_read_map: reading map sss auto.home2
> parse_init: parse(sun): init gathered global options: (null)
> lookup_read_map: map read not needed, so not done
> lookup_nss_read_map: reading map files auto.home2
> file map /etc/auto.home2 not found
> st_ready: st_ready(): state = 4 path /home/nfs
> handle_packet: type = 3
> handle_packet_missing_indirect: token 129, name mv, request pid 14994
> attempting to mount entry /home/nfs/mv
> lookup_mount: lookup(sss): looking up mv

Don't know what that's about, looking up key mv and finding flg?

> lookup_mount: lookup(sss): flg -> rw,soft 192.168.55.1:/nfsexport/home/&
> parse_mount: parse(sun): expanded entry: rw,soft
> 192.168.55.1:/nfsexport/home/flg

There's a missing - to introduce the mount options.
What autofs is complaining about is, without the leading -, it's
looking for a hostname which isn't allowed to have any spaces.
Since there's no - to introduce the mount options it thinks "rw,soft 192.168.55.1" as the host name string.

> parse_mount: parse(sun): gathered options: 

As we see it found no options.

> validate_location: invalid character " " found in location rw,soft
> 192.168.55.1:/nfsexport/home/flg

And this is the mount location, that in this case should be
hostname:<path>.

Ian

Comment 5 Ian Kent 2015-03-27 01:30:53 UTC
Looking at this bug again the problem appears to be no
more than an error in the map.

After pointing this out there's been no further response
so I'm closing this NOTABUG.