Project

General

Profile

Actions
Copy link

Bug #3587

closed

Archives entry is missing in LDAP, leading to error when creating rules.

Added by Nicolas PERRON over 11 years ago. Updated over 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
Web - Maintenance
Target version:
2.4.6
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When Trying to create a new Rule, I have an error Can't execute LDAP request. Into the log file */var/log/rudder/webapp/2013_05_15.stderrout.log

[2013-05-15 07:35:45] ERROR com.normation.ldap.sdk.RWPooledSimpleAuthConnectionProvider - Can't execute LDAP request
com.unboundid.ldap.sdk.LDAPSearchException: no such object
    at com.unboundid.ldap.sdk.LDAPConnection.search(LDAPConnection.java:3112) ~[unboundid-ldapsdk-2.3.1.jar:2.3.1]
[2013-05-15 07:35:45] ERROR com.normation.rudder.web.components.popup.CreateOrCloneRulePopup - An error occurred while saving the Rule:Can't execute LDAP request

Neverthless, I still can add new groups or Directives...

Actions
Copy link
 #1

Updated by François ARMAND over 11 years ago

  • Category set to Web - Maintenance
  • Assignee set to François ARMAND
  • Target version set to 2.6.1

I can not reproduce that on other fresh installation.

So something went wrong with that installation, and actually, the LDAP DIT is broken: there is no "ou=Rules,..." object, and so Rudder can't work.
"Simply" adding back that object and its children make rudder work again.

Normally, there is a check for that, that does not work - see bug #3588)

I'm going to relaunch snapshot-2.6 CI task to see if it's reproducible, or was "just" bad luck.

Actions
Copy link
 #2

Updated by François ARMAND over 11 years ago

  • Status changed from New to Discussion

The new snapshot works as expected, so it should be some cosmic ray not being nice with us.

Actions
Copy link
 #3

Updated by François ARMAND over 11 years ago

OK, so the actual problem is that "ou=Archives" is not created, and that combined #3588 and with a bug in UnboundID that try to move object even if the destination is not present leads to the suppression of rules, and then to the errors.

So, easy workaround (and correction): add in bootstrap.ldif "ou=Archives,ou=Rudder,cn=rudder-configuration".

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 11 years ago

  • Status changed from Discussion to In progress
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Target version changed from 2.6.1 to 2.4.6

This bug impacts 2.4 too, retargeting this issue

We also need to make a migration script to include that change.

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 11 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/211
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 11 years ago

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

Updated by Anonymous over 11 years ago

Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 11 years ago

  • Subject changed from On a fresh rudder 2.6.0 installation after having created a MOTD Directive, an error about LDAP appears when trying to make a new Rule (Can't execute LDAP request) to Archives entry is missing in LDAP, leading to error when creating rules.
Actions
Copy link
 #9

Updated by Nicolas PERRON over 11 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF