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 1382603

Summary: autofs map resolution doesn't work offline
Product: Red Hat Enterprise Linux 6 Reporter: Jakub Hrozek <jhrozek>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED ERRATA QA Contact: Steeve Goveas <sgoveas>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.9CC: ddas, grajaiya, jhrozek, lslebodn, mkosek, mniranja, mzidek, pbrezina, sgoveas, sssd-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.13.3-42.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1382602 Environment:
Last Closed: 2017-03-21 09:58:27 UTC Type: ---
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: 1382602    
Bug Blocks:    

Description Jakub Hrozek 2016-10-07 07:08:55 UTC 
+++ This bug was initially created as a clone of Bug #1382602 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/3140

to reproduce the autofs maps failure:
    * automount -m      # to verify the maps are there
    * pkill -USR1 sssd  # make sssd go offline
    * automount -m      # to verify the maps are there
Comment 1 Jakub Hrozek 2016-10-07 07:10:55 UTC 
master: b9e155da725e711ab306ca8a96e3ba6fbda41a3a
Comment 6 Niranjan Mallapadi Raghavender 2016-12-15 05:44:50 UTC 
Versions:
[root@auto-hv-02 db]# rpm -qa | grep sssd
sssd-ldap-1.13.3-52.el6.x86_64
sssd-krb5-common-1.13.3-52.el6.x86_64
sssd-ad-1.13.3-52.el6.x86_64
sssd-krb5-1.13.3-52.el6.x86_64
sssd-proxy-1.13.3-52.el6.x86_64
sssd-ipa-1.13.3-52.el6.x86_64
sssd-tools-1.13.3-52.el6.x86_64
python-sssdconfig-1.13.3-52.el6.noarch
sssd-common-1.13.3-52.el6.x86_64
sssd-common-pac-1.13.3-52.el6.x86_64
sssd-1.13.3-52.el6.x86_64
sssd-client-1.13.3-52.el6.x86_64


[root@auto-hv-02 db]# 
Red Hat Enterprise Linux Server release 6.9 Beta (Santiago)

automount -m

[root@auto-hv-02 db]# automount -m

autofs dump map information
===========================

global options: none configured

Mount point: /misc

source(s):

  instance type(s): file 
  map: /etc/auto.misc

  cd | -fstype=iso9660,ro,nosuid,nodev  :/dev/cdrom


Mount point: /net

source(s):

  type: hosts

  winsrv1.juno.test | (null)
  auto-hv-02.idmqe.lab.eng.bos.redhat.com | (null)
  localhost | (null)


Mount point: /-

source(s):

  instance type(s): sss 
  map: auto.direct

  /project2 | -fstype=nfs,rw vm-idm-020.lab.eng.pnq.redhat.com:/project2
  /project1 | -fstype=nfs,rw vm-idm-020.lab.eng.pnq.redhat.com:/project1


Mount point: /home

source(s):

  instance type(s): sss 
  map: auto.home

  * | -rw vm-idm-020.lab.eng.pnq.redhat.com:/home/&



[root@auto-hv-02 db]# ps aux | grep sssd
root      2607  0.0  0.0 227824  2692 ?        Ss   11:10   0:00 /usr/sbin/sssd -f -D
root      2608 22.8  1.7 407732 70276 ?        S    11:10   0:32 /usr/libexec/sssd/sssd_be --domain juno.test --uid 0 --gid 0 --debug-to-files
root      2609  0.0  0.7 231092 27952 ?        S    11:10   0:00 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --debug-to-files
root      2610  0.0  0.0 210784  3368 ?        S    11:10   0:00 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --debug-to-files
root      2611  0.0  0.0 214592  3336 ?        S    11:10   0:00 /usr/libexec/sssd/sssd_autofs --uid 0 --gid 0 --debug-to-files
root      2644  0.0  0.0 103332   844 pts/1    S+   11:13   0:00 grep sssd


Kill sssd process

[root@auto-hv-02 db]#  pkill -USR1 sssd


[root@auto-hv-02 db]# automount -m

autofs dump map information
===========================

global options: none configured

Mount point: /misc

source(s):

  instance type(s): file 
  map: /etc/auto.misc

  cd | -fstype=iso9660,ro,nosuid,nodev  :/dev/cdrom


Mount point: /net

source(s):

  type: hosts

  winsrv1.juno.test | (null)
  auto-hv-02.idmqe.lab.eng.bos.redhat.com | (null)
  localhost | (null)


Mount point: /-

source(s):

  instance type(s): sss 
  map: auto.direct

  /project2 | -fstype=nfs,rw vm-idm-020.lab.eng.pnq.redhat.com:/project2
  /project1 | -fstype=nfs,rw vm-idm-020.lab.eng.pnq.redhat.com:/project1


Mount point: /home

source(s):

  instance type(s): sss 
  map: auto.home

  * | -rw vm-idm-020.lab.eng.pnq.redhat.com:/home/&
Comment 8 errata-xmlrpc 2017-03-21 09:58:27 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/RHBA-2017-0632.html