Actions
Bug #3588
closed
Bootstrap check for LDAP DIT lies
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Even if the LDAP DIT is incorrect (missing ou=rules for example), the check say "everything is well".
Updated by François ARMAND over 11 years ago
Actually, the problem is that in 2.6, we switch to "object" in DIT. Objects are lazy loaded, so ARCHIVES (and others) never get the opportunity to be initialized (and so, to register their OU) before LDAP check.
Forcing to register object in the DIT object lead to good inistialization.
Updated by François ARMAND over 11 years ago
- Status changed from 8 to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/212
Updated by Nicolas CHARLES over 11 years ago
- Status changed from Pending technical review to Pending release
This has been merged !
Updated by Vincent MEMBRÉ over 11 years ago
- Status changed from Pending release to Released
This ticket has been adressed in the 2.6.1 release of Rudder.
The ChangeLog is available here: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
Actions