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 1166457 - Autofs unable to mount indirect after attempt to mount wildcard
Summary: Autofs unable to mount indirect after attempt to mount wildcard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: autofs
Version: 7.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Ian Kent
QA Contact: Yongcheng Yang
Jaromir Hradilek
URL:
Whiteboard:
Depends On: 1163957
Blocks: 1133060 1205790
TreeView+ depends on / blocked
 
Reported: 2014-11-21 02:16 UTC by Ian Kent
Modified: 2019-03-22 07:25 UTC (History)
5 users (show)

Fixed In Version: autofs-5.0.7-49
Doc Type: Bug Fix
Doc Text:
Cause: when an "ls *" is done of the root of an indirect mount, autofs will attempt to literally mount the key '*' causing it to be added to the negative cache. Consequence: if this is done before a valid mount, autofs fails on further mount attempts inside the mountpoint, valid or not. Fix: fixed by checking for and not adding the wildcard key when updating the negative cache. Result: the wildcard map entry continues to function following a 'ls *' within the root of an autofs mountpoint.
Clone Of: 1163957
Environment:
Last Closed: 2015-11-19 13:00:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch - make negative cache update consistent for all lookup modules (2.95 KB, patch)
2015-05-25 01:29 UTC, Ian Kent 		no flags Details | Diff
Patch - ensure negative cache isn't updated on remount (1.49 KB, patch)
2015-05-25 01:30 UTC, Ian Kent 		no flags Details | Diff
Patch - dont add wildcard to negative cache (1.35 KB, patch)
2015-05-25 01:31 UTC, Ian Kent 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2417 0 normal SHIPPED_LIVE Moderate: autofs security, bug fix and enhancement update 2015-11-19 11:23:21 UTC

Comment 1 Ian Kent 2015-05-25 01:29:37 UTC 
Created attachment 1029319 [details]
Patch - make negative cache update consistent for all lookup modules
Comment 2 Ian Kent 2015-05-25 01:30:31 UTC 
Created attachment 1029320 [details]
Patch - ensure negative cache isn't updated on remount
Comment 3 Ian Kent 2015-05-25 01:31:28 UTC 
Created attachment 1029321 [details]
Patch - dont add wildcard to negative cache
Comment 5 XuWang 2015-08-27 08:41:25 UTC 
run /CoreOS/autofs/Regression/bz1163957-unable-mount-indirect-after-ls-with-wildcard for autofs-5.0.7-53.el7, seems good.

the previous version output:
:: [   FAIL   ] :: Command 'ls -ld /automount/dir{1,2}' (Expected 0, got 2)

the autofs-5.0.7-53.el7 output:

[03:26:56 root@ ~~]# ls -ld /automount/*
ls: cannot access /automount/*: No such file or directory
:: [   PASS   ] :: Running 'ls -ld /automount/*' (Expected 2, got 2)
--------------------------------------------------------------------------------
[03:26:56 root@ ~~]# ls -ld /automount/dir{1,2}
drwxr-xr-x. 2 root root 6 Aug 27 03:26 /automount/dir1
drwxr-xr-x. 2 root root 6 Aug 27 03:26 /automount/dir2
:: [   PASS   ] :: Running 'ls -ld /automount/dir{1,2}' (Expected 0, got 0)

also run stress, bugzillas, regressions, connectathon for autofs-5.0.7-53.el7, covered ppc64, x86_64, s390x, ppc64le no new issues.

I think I can set the status of this bug to be verified.
Comment 8 errata-xmlrpc 2015-11-19 13:00:45 UTC 
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://rhn.redhat.com/errata/RHSA-2015-2417.html
Note You need to log in before you can comment on or make changes to this bug.