Bug #5705

A Rudder upgrade that leads to a different BDB version usage in slapd fails

Added by Matthieu CERDA over 5 years ago. Updated about 5 years ago.

Target version:
User visibility:
Effort required:


We have a post-install script bit that takes care of this, but it does not work properly.

We redirect things to /dev/null a bit too greedily it seems...

Related issues

Related to Rudder - Architecture #3725: Change the output of Rudder packages to be less deceptiveReleased2013-07-12Jonathan CLARKEActions
Related to Rudder - Bug #5575: Upgrading rudder-inventory-ldap between two major OS versions makes slapd unable to operate because of BerkeleyDBReleased2014-09-26Jonathan CLARKEActions

Updated by Matthieu CERDA over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Matthieu CERDA to Jonathan CLARKE
  • % Done changed from 0 to 100
  • Pull Request set to

Updated by Matthieu CERDA over 5 years ago

This change has been introduced in #3725... It has been present since quite a lot of time...

The good thing is, as it is located in the post-install script, an upgrade that contains the fix from this ticket will upgrade the database properly :)


Updated by Matthieu CERDA over 5 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:4318cfd9c1629835f94e497b27d22d8078cc9e20.


Updated by Jonathan CLARKE over 5 years ago

Applied in changeset commit:d00499079fa93af60a2243696522200670432796.


Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.7 and 2.11.4, which were released today.


Updated by Benoît PECCATTE about 5 years ago

  • Project changed from packages to Rudder
  • Category set to Packaging

Also available in: Atom PDF