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 1695575 - sssd service is starting before network service
Summary: sssd service is starting before network service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 8.0
Assignee: Tomas Halman
QA Contact: sssd-qe
URL:
Whiteboard: sync-to-jira
Depends On: 1406678
Blocks: 1420851 1472344 1594286 1647919
TreeView+ depends on / blocked
 
Reported: 2019-04-03 11:50 UTC by Jakub Hrozek
Modified: 2020-05-04 11:09 UTC (History)
23 users (show)

Fixed In Version: sssd-2.2.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1406678
Environment:
Last Closed: 2019-11-05 22:34:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4327 0 None None None 2020-05-04 11:09:24 UTC
Github SSSD sssd issues 4493 0 None None None 2020-05-04 11:09:37 UTC
Red Hat Product Errata RHSA-2019:3651 0 None None None 2019-11-05 22:35:26 UTC

Comment 2 shridhar 2019-09-09 10:33:31 UTC 
Verified with 
sssd-2.2.0-18.el8.x86_64
sssd-dbus-2.2.0-18.el8.x86_64

[root@vm-idm-004 ~]# cat /etc/sssd/sssd.conf 

[sssd]
config_file_version = 2
services = nss, pam
domains = LDAP

[nss]
filter_groups = root
filter_users = root

[domain/LDAP]
debug_level=0xFFF0
id_provider = ldap
ldap_uri = ldap://vm-idm-002.lab.eng.pnq.redhat.com
ldap_search_base = dc=example,dc=com
ldap_tls_cacert = /etc/openldap/certs/cacert.asc
enumerate = true




[root@vm-idm-004 ~]# cat test.sh 
#!/bin/bash
echo "Stopping dir srv on ldap-server"
ssh vm-idm-002.lab.eng.pnq.redhat.com systemctl stop dirsrv 
echo "Updating sssd service with SIGUSR1"
kill -10 `pidof sssd`
echo "sssctl domain-status LDAP"
sssctl domain-status LDAP
sleep 1s
touch /etc/resolv.conf
sleep 3s
echo "Starting dir srv on ldap-server"
ssh vm-idm-002.lab.eng.pnq.redhat.com systemctl start  dirsrv
sleep 6s
sssctl domain-status LDAP
[root@vm-idm-004 ~]# 




[root@vm-idm-004 ~]# sh test.sh 
Stopping dir srv on ldap-server
Updating sssd service with SIGUSR1
sssctl domain-status LDAP
Online status: Offline

Active servers:
LDAP: vm-idm-002.lab.eng.pnq.redhat.com

Discovered LDAP servers:
- vm-idm-002.lab.eng.pnq.redhat.com

Starting dir srv on ldap-server
Online status: Online

Active servers:
LDAP: vm-idm-002.lab.eng.pnq.redhat.com

Discovered LDAP servers:
- vm-idm-002.lab.eng.pnq.redhat.com
Comment 4 errata-xmlrpc 2019-11-05 22:34:23 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/RHSA-2019:3651
Note You need to log in before you can comment on or make changes to this bug.