Project

General

Profile

Actions
Copy link

Bug #3807

closed

MIgration from Rudder 2.3.13 to 2.6.3 could not work if indexes which does not exist are added in the slapd.conf

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

Status:
Rejected
Priority:
1 (highest)
Assignee:
-
Category:
Packaging
Target version:
2.6.20
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

During a migration from a server Rudder 2.3.13 to 2.6.3, the migration didn't work because of LDAP configuration. It stopped at the use of an index "isActivated":

[...]
The Rudder OpenLDAP schema is not up to date.
You will see some warnings about UNKNOWN attributeDescription.
Updating...
...done.
Some cpuSpeed attributes were converted to integers in the LDAP database
slapd[4543]: [INFO] Using /etc/default/slapd for configuration
slapd[4548]: [INFO] Killing OpenLDAP with force...
slapd[4550]: [OK] slapd process killed with force (PID 1110)
slapd[4551]: [INFO] Killing OpenLDAP replication with force...
slapd[4557]: [INFO] Found no slurpd process running
/opt/rudder/etc/openldap/slapd.conf: line 84: index attribute "isActivated" undefined
slapadd: bad configuration file!
dpkg : erreur de traitement de rudder-inventory-ldap (--configure) :
[...]
Actions
Copy link

Also available in: Atom PDF