Bug 132105

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
Gecko/20031007

Description of problem:
(Note that this problem apparently also exists in earlier versions of
autofs -- e.g. autofs-3.1.7-41 in RHEL 3.0 Update 2. We have only just
noticed it due to the new functionality in RHEL 3.0 Update 3 which
seeks out the best connection.)

If you have an automount map entry with multiple potential mount
sources and the automounter fails to mount one of those entries, it
will return a failure without attempting to mount the other entries.


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

How reproducible:
Always

Steps to Reproduce:
1. Add "  localhost:/path/does/not/exist/&" as a secondary mount
source to the end of an automount map entry.
2. Restart autofs (e.g., `service autofs restart`)
3. Make sure that the automount point not currently mounted (e.g.,
`umount /mnt/auto/filesystem`).
3. Attempt to change directories to the automount point (e.g., `cd
/mnt/auto/filesystem`). autofs will determine that the localhost entry
is the closest on the network, attempt to mount it, fail, and not
attempt to mount the automount entry from other mount sources.

Actual Results:  # verify /apps/vendor/bin not mounted
% ls /apps/vendor
./  ../

# now automount /apps/vendor/bin and verify
% ls -ld /apps/vendor/bin
drwxr-xr-x    3 toolsadm daemon      12288 Sep  2 12:03 /apps/vendor/bin/

# edit /etc/auto.appsvendor
% vi /etc/auto.appsvendor

# Verify /apps/vendor/bin entry has been updated
% grep ^bin /etc/auto.appsvendor
bin ahfil03:/vol/vol0_03/software/vendor/&   
ahfil01:/vol/vol0_01/software/vendor/& localhost:/path/does/not/exist/&

# restart autofs
% service autofs restart
umount2: Device or resource busy                           [  OK  ]
umount: /apps/public: device is busy
umount2: Device or resource busy
umount: /home: device is busy

Starting automount:                                        [  OK  ]

# unmount /apps/vendor/bin
% umount /apps/vendor/bin

# verify /apps/vendor/bin not mounted
% ls /apps/vendor
./  ../

# try to automount /apps/vendor/bin and verify
% ls -ld /apps/vendor/bin
/bin/ls: /apps/vendor/bin: No such file or directory

# check out syslog entries
% tail -4 /var/log/messages
Sep  8 15:27:34 lnxtst04 automount[7097]: >> mount: special device
/path/does/not/exist/bin does not exist
Sep  8 15:27:34 lnxtst04 automount[7097]: failed to mount /apps/vendor/bin
Sep  8 15:27:34 lnxtst04 automount[7099]: >> mount: special device
/path/does/not/exist/bin does not exist
Sep  8 15:27:34 lnxtst04 automount[7099]: failed to mount /apps/vendor/bin



Expected Results:  The mount attempt should have failed over to one of
the good entries and we should have been able to access
/apps/vendor/bin normally.

Additional info: