Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 219434

Summary:	autofs failed to mount using wildkey and replicated configuration
Product:	Red Hat Enterprise Linux 3	Reporter:	hyunmo kang <hyunmo.kang>
Component:	autofs	Assignee:	Jeff Moyer <jmoyer>
Status:	CLOSED WONTFIX	QA Contact:	Brock Organ <borgan>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	3.8	CC:	djoo, ikent
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-01-17 20:04:16 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:

Description hyunmo kang 2006-12-13 01:34:18 UTC

Description of problem:
automount fails to mount using a certain automount map.

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

How reproducible:
always

Steps to Reproduce:
1.
configure automount map as following

#auto.master
/words auto.words

#auto.words
* host1:/a/& host1:/b/& host2:/c/& host2:/d/&

2.
say words are classified into seperate location in an alphabetical order

3.
access "/words/bat" or "/words/dog"

Actual results:
mount fails

Expected results:

Additional info:
i have looked into source code.
when some path on a host is failed to mount, 
any trial to mount different path on the same host is ignored.
that, however, should not happen in my configuration.
on solaris and hp-ux system, i captured nfs packets and they try every location 
until they get successful mount.

Comment 1 Jeff Moyer 2007-01-17 20:04:16 UTC

Given that this is a deviation from the behaviour under Solaris, this is
certainly a bug.  However, I do not believe this meets the RHEL 3.9 release
criteria.  As such, the issue will not be addressed.  I will open a bugzilla
against RHEL 4 for this issue.