Bug #4348
closed
Missing Node Configuration entry in LDAP prevents Rudder from starting
Added by François ARMAND over 9 years ago.
Updated over 9 years ago.
Category:
Web - Config management
Description
If someone remove the "ou=Nodes Configuration" object in LDAP, nothing is done to add-it back when Rudder restart, leading to a broken server (and an LDAP command line to issue).
=> add that OU to the necessary objects.
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/411
- Target version changed from 2.6.10 to 2.6.11
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Subject changed from Missing Node Configuration in LDAP leads to non-bootable Rudder to Missing Node Configuration entry in LDAP prevents Rudder from starting
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:
Also available in: Atom
PDF