Actions
Bug #5705
closed
A Rudder upgrade that leads to a different BDB version usage in slapd fails
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
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...
Updated by Matthieu CERDA about 10 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 https://github.com/Normation/rudder-packages/pull/512
Updated by Matthieu CERDA about 10 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 about 10 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:4318cfd9c1629835f94e497b27d22d8078cc9e20.
Updated by Jonathan CLARKE about 10 years ago
Applied in changeset commit:d00499079fa93af60a2243696522200670432796.
Updated by Vincent MEMBRÉ about 10 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.
- Announcement 2.10 2.11
- Changelog 2.10 2.11
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Actions