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 1680582

Summary: Sanitize autofs logging
Product: Red Hat Enterprise Linux 7 Reporter: Marko Myllynen <myllynen>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED ERRATA QA Contact: Kun Wang <kunwan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: xzhou
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: autofs-5.0.7-105.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1689466 (view as bug list) Environment:
Last Closed: 2019-08-06 13:10:29 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:
Bug Depends On:    
Bug Blocks: 1689466    

Description Marko Myllynen 2019-02-25 11:04:54 UTC
Description of problem:
With logging = verbose we see entries like:

Feb 18 13:46:13 localhost automount: 1 remaining in /-
Feb 18 13:46:16 localhost automount: 1 remaining in /-
Feb 18 13:46:19 localhost automount: 1 remaining in /-
Feb 18 13:46:22 localhost automount: 1 remaining in /-

These would be more appropriate for logging = debug level, please consider adjusting the log level for these messages. Thanks.

Version-Release number of selected component (if applicable):
autofs-5.0.7-99.el7.x86_64

Comment 3 Kun Wang 2019-04-12 05:52:44 UTC
Verified based on below test result:


#####################################
# On autofs-5.0.7-104.el7           #
#####################################
:: [ 01:51:46 ] :: [  BEGIN   ] :: Bug 1680582 - Sanitize autofs logging :: actually running 'grep -r "1 remaining in" /var/log/messages'
Apr 12 01:51:44 hp-dl180g6-01 automount: 1 remaining in /nfs
:: [ 01:51:46 ] :: [   FAIL   ] :: Bug 1680582 - Sanitize autofs logging (Expected 1, got 0)

#####################################
# On autofs-5.0.7-105.el7 or later: #
#####################################
:: [ 01:43:20 ] :: [  BEGIN   ] :: Bug 1680582 - Sanitize autofs logging :: actually running 'grep -r "1 remaining in" /var/log/messages'
:: [ 01:43:20 ] :: [   PASS   ] :: Bug 1680582 - Sanitize autofs logging (Expected 1, got 1)

Comment 5 errata-xmlrpc 2019-08-06 13:10:29 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://access.redhat.com/errata/RHBA-2019:2250