Project

General

Custom queries

Profile

Actions
Copy link

Bug #10067

closed

If an LDAP attribute is missing the related LDAP errors are not reported in UI (silent fail)

Added by François ARMAND over 8 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Web - UI & UX
Target version:
5.0.15
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Priority:
58
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

The reported error is:

[2017-01-24 16:53:01] ERROR com.normation.ldap.sdk.RwLDAPConnection - Exception ignored (by configuration) when trying to modify entry 'directiveId=61d6bce5-116c-4e0b-85bf-93bdecc3eef5,activeTechniqueId=ab90f00a-d206-42dd-aa1b-9b493f2b4932,techniqueCategoryId=applications,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration'.  Reported exception was: serializedTags: attribute type undefined
com.unboundid.ldap.sdk.LDAPException: serializedTags: attribute type undefined
    at com.unboundid.ldap.sdk.LDAPConnection.modify(LDAPConnection.java:2513) ~[unboundid-ldapsdk-2.3.6.jar:2.3.6]
    at com.normation.ldap.sdk.RwLDAPConnection$$anonfun$10$$anonfun$apply$7.apply(LDAPConnection.scala:541) ~[scala-ldap-4.1.0~beta2-SNAPSHOT.jar:na]
    at com.normation.ldap.sdk.RwLDAPConnection$$anonfun$10$$anonfun$apply$7.apply(LDAPConnection.scala:541) ~[scala-ldap-4.1.0~beta2-SNAPSHOT.jar:na]
    at scala.util.control.Exception$Catch.apply(Exception.scala:103) ~[na:na]
 ....

That error certainly should not be ignored.
It may happen since the start of (Rudder) times.

Actions
Copy link
 #12

Updated by François ARMAND over 5 years ago

This one is only reported with OpenLDAP, not with the test server in unboundID SDK.

Actions
Copy link
 #13

Updated by François ARMAND over 5 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/2583
Actions
Copy link
 #14

Updated by François ARMAND over 5 years ago

OK, actually I'm not sure why we ignore most of the case set to be ignored by default here:

NO_SUCH_ATTRIBUTE => it's clearly a failure in all case, we are adding something not in the schem
UNDEFINED_ATTRIBUTE_TYPE => same
INVALID_ATTRIBUTE_SYNTAX => we are trying to add for ex a bool to a string, clearly an error.
INVALID_DN_SYNTAX => clearly an error we want to catch
ENCODING_ERROR => same.

Perhaps keep that one:

ATTRIBUTE_OR_VALUE_EXISTS, ENTRY_ALREADY_EXISTS => for idempotency

Actions
Copy link
 #15

Updated by François ARMAND over 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.15 which was released today.

Actions
Copy link

Also available in: Atom PDF