Project

General

Profile

Actions

Bug #3588

closed

Bootstrap check for LDAP DIT lies

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

Status:
Released
Priority:
1
Category:
Web - Maintenance
Target version:
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".


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #3589: Force init of LDAP DIT inventory objectsReleasedNicolas CHARLES2013-05-15Actions
Actions #1

Updated by François ARMAND almost 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.

Actions #2

Updated by François ARMAND almost 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
Actions #3

Updated by Nicolas CHARLES almost 11 years ago

  • Status changed from Pending technical review to Pending release

This has been merged !

Actions #4

Updated by Vincent MEMBRÉ almost 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

Also available in: Atom PDF