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 1315958

Summary: slapd fails to start on boot
Product: Red Hat Enterprise Linux 7 Reporter: Arpit Tolani <atolani>
Component: openldapAssignee: Matus Honek <mhonek>
Status: CLOSED ERRATA QA Contact: Patrik Kis <pkis>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: nkinder, pkis, tburns
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: system configured without NetworkManager Consequence: slapd fails to wait on NetworkManager-wait-online.service when booting Fix: use systemd's network-online.target Result: slapd correctly starts on boot even when a system is configured without NetworkManager
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 23:41:48 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:

Description Arpit Tolani 2016-03-09 06:45:27 UTC
Description of problem:
After upgrade to RHEL 7.2, slapd service no longer starts on boot. Doing service slapd start after the system is up, brings it right up.

Version-Release number of selected component (if applicable):
openldap-servers-2.4.40-8.el7.x86_64

How reproducible:
Everytime in customer environment. 

Steps to Reproduce:
1. Upgrade to this version of openldap.
2. Reboot.
3. Watch the boot process (slapd fails to start).
4. Run systemctl status slapd.service.
  
Actual results:
Does not start.

Expected results:
Worked fine before upgrade.

Additional info:
This is related to https://bugzilla.redhat.com/show_bug.cgi?id=946921

After updating openldap-servers package, /usr/lib/systemd/system/slapd.service file got modified as :

/usr/lib/systemd/system/slapd.service
[Unit]
Description=OpenLDAP Server Daemon
After=syslog.target NetworkManager-wait-online.service	<------

I think the correct solution for this should be to use After=syslog.target network-online.target

Customer tried to change it to network-online.target & it worked.

Comment 6 Matus Honek 2016-10-11 12:13:26 UTC
*** Bug 1383666 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2016-11-03 23:41:48 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-2016-2163.html