Project

General

Profile

Actions
Copy link

Bug #10664

closed

Configuration file of Rudder mention that we may change "LDAP DIT configuration", which is wrong

Added by Nicolas CHARLES over 7 years ago. Updated over 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
System integration
Target version:
4.1.10
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Priority:
43
Name check:
Fix check:
Regression:

Description

We cannot change the LDAP DIT configuration and expect Rudder to keep working, even more after #8017 which hardcode these values

We need to update comments in the file to make sure nobody get tricked by this message

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #8017: Adding an authorized network when "common-root" directive is missing seems to work, but actually failsReleasedNicolas CHARLESActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES over 7 years ago

  • Related to Bug #8017: Adding an authorized network when "common-root" directive is missing seems to work, but actually fails added
Actions
Copy link
 #2

Updated by François ARMAND over 7 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
Actions
Copy link
 #3

Updated by François ARMAND over 7 years ago

  • Priority changed from 0 to 24
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions
Copy link
 #6

Updated by Benoît PECCATTE over 7 years ago

  • Priority changed from 24 to 38
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
  • Priority changed from 38 to 37
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.24 to 3.1.25
  • Priority changed from 37 to 36
Actions
Copy link
 #10

Updated by Benoît PECCATTE about 7 years ago

  • Priority changed from 36 to 46
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.25 to 387
  • Priority changed from 46 to 45
Actions
Copy link
 #12

Updated by Nicolas CHARLES almost 7 years ago

  • Target version changed from 387 to 4.1.10
Actions
Copy link
 #13

Updated by Nicolas CHARLES almost 7 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions
Copy link
 #14

Updated by Nicolas CHARLES almost 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1821
Actions
Copy link
 #15

Updated by Rudder Quality Assistant almost 7 years ago

  • Assignee changed from François ARMAND to Nicolas CHARLES
Actions
Copy link
 #16

Updated by Nicolas CHARLES almost 7 years ago

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

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released
  • Priority changed from 45 to 43

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Actions
Copy link

Also available in: Atom PDF