Project

General

Profile

Actions
Copy link

Bug #4348

closed

Missing Node Configuration entry in LDAP prevents Rudder from starting

Added by François ARMAND almost 11 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
2.6.11
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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.

Actions
Copy link
 #1

Updated by François ARMAND almost 11 years ago

  • 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
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.10 to 2.6.11
Actions
Copy link
 #3

Updated by François ARMAND almost 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 11 years ago

  • Subject changed from Missing Node Configuration in LDAP leads to non-bootable Rudder to Missing Node Configuration entry in LDAP prevents Rudder from starting
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:

Actions
Copy link

Also available in: Atom PDF