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.

+++ 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

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