(In reply to fjayalat from comment #0)
> Description of problem:
> 
> Raising this Bugzilla to address the issue discussed in :
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1189767
> https://fedorahosted.org/sssd/ticket/3080
> 
> 
> Version-Release number of selected component (if applicable):
> RHEL 7.3 ( Customer is in a secure env so do not have the sosreport. Given
> they have upgraded to 7.3 , assuming they have the latest version of SSSD)
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:
> 
> 
> My workaround on newly installed or upgraded RHEL 7.3 systems is the
> following, and so far is working reliably:
> 
> sed -i '/EnvironmentFile.*/aExecStartPre=\/bin\/sleep 10'
> /etc/systemd/system/multi-user.target.wants/sssd.service
> cat << EOF > /etc/init.d/restartautofs
> #! /bin/sh
> 
> ### BEGIN INIT INFO
> # Provides: restartautofs
> # Required-Start: 
> # Required-Stop: 
> # Should-Start: 
> # Should-Stop: 
> # Default-Start: 2 3 4 5
> # Default-Stop: 0 1 6
> # Short-Description: Automounts filesystems on demand
> # Description: Automounts filesystems on demand
> ### END INIT INFO
> 
> # Location of the automount daemon and the init directory
> #
> PROG=automount
> DAEMON=/usr/sbin/$PROG
> sleep 10
> /etc/init.d/autofs restart
May I know why they use initscripts on rhel7

autofs on rhel7 provide service file.

sh$ rpm -ql autofs | grep service
/usr/lib/systemd/system/autofs.service

btw there were several related bug reports such as https://fedorahosted.org/sssd/ticket/3080 or https://fedorahosted.org/sssd/ticket/3140 fixed recently. I think that providing a test package with these fixes has quite a high chance of fixing or at least remediating the issue.

Could you cherry pick and apply the patches for the customer or would you like me to build a test package with those patches?

We should small steps. Firstly they should test with systemd version of initscripts and then we try providing scratch builds for #3140 or #3080(which is still not fixed in upstream). But I can provide scratch builds.

I'm having the same issue. I'm working around it with a NM dispatcher script:

# cat /etc/NetworkManager/dispatcher.d/28-autofs
#!/bin/bash

if [ -x /usr/bin/logger ]; then
  LOGGER="/usr/bin/logger -s -p user.notice -t NetworkManagerDispatcher"
else
  LOGGER=echo
fi

if [ "$2" = "up" -o "$2" = "vpn-up" ] || [ "$2" = "down" -o "$2" = "vpn-down" ]; then
    # We may be running at the same time as the initial boot start of
    # autofs.  restart can cause problems, so do a reload and start
    $LOGGER "performing autofs reload"
    systemctl reload autofs.service
    $LOGGER "performing autofs start"
    systemctl start autofs.service
fi

(In reply to Orion Poplawski from comment #18)
> I'm having the same issue. I'm working around it with a NM dispatcher script:
> 
> # cat /etc/NetworkManager/dispatcher.d/28-autofs
> #!/bin/bash
> 
> if [ -x /usr/bin/logger ]; then
>   LOGGER="/usr/bin/logger -s -p user.notice -t NetworkManagerDispatcher"
> else
>   LOGGER=echo
> fi
> 
> if [ "$2" = "up" -o "$2" = "vpn-up" ] || [ "$2" = "down" -o "$2" =
> "vpn-down" ]; then
>     # We may be running at the same time as the initial boot start of
>     # autofs.  restart can cause problems, so do a reload and start
>     $LOGGER "performing autofs reload"
>     systemctl reload autofs.service
>     $LOGGER "performing autofs start"
>     systemctl start autofs.service
> fi
This will not be necessary with fix from https://fedorahosted.org/sssd/ticket/3140

You might try fixed version of sssd; upstream version is 1.14.2
https://copr.fedorainfracloud.org/coprs/g/sssd/sssd-1-14/

And it should be also part on next update in 7.3 -> BZ1398673

Do we have ETA on when sssd-1.14.0-43.el7_3.10 will be available in RHEL7.3 ?

Hi,
given that the affected party confirmed that the packages with the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1398673 corrected their issue, I'm marking this bugzilla as a duplicate of #1398673.

Please note that upstream corrected several different issues with similar symptoms, notably upstream #3080, which is not included in downstream #1398673.

*** This bug has been marked as a duplicate of bug 1398673 ***