Project

General

Profile

Actions
Copy link

Bug #13941

closed

Bad LDAP credential after upgrading to 5.0

Added by Nicolas CHARLES over 5 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
6.1.19
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
57
Name check:
Fix check:
Regression:

Description

(was: Broken Rudder after upgrading from 4.2 to 5.0)

A case happened when a user upgraded from 4.2.6 to 5.0.2, and resulted in a broken Rudder:
  • web interface didn't start, due to invalid ldap credentials
  • agent couldn't fix the credentials, as policies are out of sync with ncf

to make matter worse, a bug in the cron edition resulted in a non-run rudder agent check

we should have something, in postinst, to ensure password are correct, even without a working agent

Actions
Copy link

Also available in: Atom PDF