Project

General

Profile

Actions
Copy link

Bug #7850

closed

Upgrading from 2.11 to 3.1.6, with a distributed setup ( external DB ), on SLES, leads to invalid config file for LDAP

Added by Nicolas CHARLES almost 9 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
1 (highest)
Assignee:
-
Category:
Server components
Target version:
3.1.22
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
34
Name check:
Fix check:
Regression:

Description

When upgrading from Rudder 2.11.quiteold to 3.1.6, the system could not run rudder-upgrade, because it failed to connect to LDAP
Indeed, the path used for the config file was /opt/rudder/etc/openldap.conf , which did not exist anymore (??)
The file /etc/default/rudder-slapd was empty, except for commented entries for IP, PORT, RUDDER_CACHESIZE
Removing this file allowed to use the proper config file (/opt/rudder/etc/openldap/slapd.conf) (weird, isn't it)

But then, rudder-upgrade still failed to connect to LDAP.
It was trying to connect using the FQDN of the host, while file /opt/rudder/etc/rudder-slapd.conf defined IP="localhost"
Replacing by IP="*" solved the issue

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #7849: rudder-upgrade does not make some check on remote sql in case of distributed setupReleasedBenoît PECCATTE2016-01-27Actions
Related to Rudder - Bug #8172: Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parametersReleasedBenoît PECCATTEActions
Actions
Copy link

Also available in: Atom PDF