Bug #13941
Updated by Benoît PECCATTE over 5 years ago
(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