Bug 2215661

Summary: The sss lookup modules handles error return incorrectly in some cases
Product: Red Hat Enterprise Linux 9 Reporter: Ian Kent <ikent>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED ERRATA QA Contact: Kun Wang <kunwan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.1CC: kunwan, pbrezina, xzhou
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: autofs-5.1.7-53.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2214444 Environment:
Last Closed: 2023-11-07 08:53:53 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: 2214444    
Bug Blocks:    

Description Ian Kent 2023-06-17 01:50:41 UTC
+++ This bug was initially created as a clone of Bug #2214444 +++

Description of problem:
The autofs sss lookup module handles error returns incorrectly in some cases.
This leads to automount not waiting for a host to become available (if it's down at the time the master map read is attempted) so that a map not found error is returned when it shouldn't be, for example the "automount -m" command.

Version-Release number of selected component (if applicable):
Current version of autofs.

--- Additional comment from Ian Kent on 2023-06-13 02:16:16 UTC ---

It's not that easy to reproduce this problem because an ldap server
needs to be setup to provide autofs map information to a client setup
to use sss. What makes it even harder is that the ldap server needs
to be down and then be started up to test the functionality.

But if this is done then an "automount -m" command to read and
list the available maps should wait for a period of time before
giving up or succeeding as the case may be.


Fortunately, since Pavel would like to be able to verify this during
sss testing, we should be able to get help with testing.

Ian

Comment 9 errata-xmlrpc 2023-11-07 08:53:53 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 (autofs bug fix and enhancement update), 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-2023:6638