Actions
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
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
Updated by Nicolas CHARLES about 8 years ago
- Related to Bug #7849: rudder-upgrade does not make some check on remote sql in case of distributed setup added
Updated by Nicolas CHARLES about 8 years ago
- Related to Bug #8172: Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters added
Updated by Nicolas CHARLES about 8 years ago
- Subject changed from Upgrading from 2.11 to 3.1.6, with a ditributed setup ( external DB ), on SLES, leads to invalid config file for LDAP to Upgrading from 2.11 to 3.1.6, with a distributed setup ( external DB ), on SLES, leads to invalid config file for LDAP
- Category changed from Packaging to Server components
- Target version set to 3.1.10
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.10 to 3.1.11
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.11 to 3.1.12
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.12 to 3.1.13
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.13 to 3.1.14
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Jonathan CLARKE about 7 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Infrequent - complex configurations | third party integrations
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by Benoît PECCATTE almost 7 years ago
- Status changed from New to Rejected
Upgrading from 2.11 is not supported anymore
Actions