Bug 238531 - autofs displays incorrect device entry for trigger mount entries
autofs displays incorrect device entry for trigger mount entries
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: autofs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ian Kent
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2007-05-01 02:17 EDT by Ian Kent
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2007-0621
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 12:30:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ian Kent 2007-05-01 02:17:30 EDT
Description of problem:

When using the internal "-hosts" autofs map against
a host with several exports the device listed in the
autofs trigger mount entries is incorrectly listed as
(null) when it should be the value "-hosts".

How reproducible:

Steps to Reproduce:
1) Ensure an entry that uses the built in "-hosts" map is
present in the master map.
2) Cause autofs to mount the export triggers by accessing
the host.
3) cat /proc/mounts to view the incorrect field of the
autofs trigger mounts.

Actual results:
(null) is displayed as the device for the mount entry.

Expected results:
-hosts displayed as the mount entry device.
Comment 1 RHEL Product and Program Management 2007-05-01 02:23:33 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 3 Ian Kent 2007-05-30 23:44:13 EDT
A patch to fix this issue has been applied and is available
in revision 0.rc2.44.
Comment 7 errata-xmlrpc 2007-11-07 12:30:32 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.