Actions
Bug #3570
closed
CFEngine internal database verification should depend on the CFEngine version as BerkeleyDB is no more used since Rudder 2.6
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Following #3564, we changed the databases checked by Rudder agent to TolyoCabinet for branch 2.6 and left it to BDB for 2.5
However, there might be cases where user might have a mixed installation, and the check would fail
We should rather do a check based on the CFEngine version ( cfengine_3_2 would be bdb, cfengine_3_3, cfengine_3_4 or cfengine_3_5 would be TC)
I'm primary targeting this to 2.4, as it is the stable release, and people might want to go fro m the stable to the bleeding edge step by step; and it seems unlikely to mix 2.3 and 2.6
Updated by Matthieu CERDA almost 11 years ago
- Status changed from New to Pending technical review
- Assignee set to Matthieu CERDA
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/121
PR available.
Updated by Matthieu CERDA almost 11 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:ac914fdc425ed1bd05fe23a4f09f6c22f5d4a609.
Updated by Jonathan CLARKE almost 11 years ago
Applied in changeset commit:98d52135c47a56b426ecfe7278212a0d8fd3c113.
Updated by Nicolas PERRON almost 11 years ago
- Subject changed from Make the cfengine internal database verification depend on the cfengine version to CFEngine internal database verification should depend on the CFEngine version as BerkeleyDB is no more used since Rudder 2.6
Updated by Nicolas PERRON almost 11 years ago
- Status changed from Pending release to Released
Updated by Benoît PECCATTE about 9 years ago
- Project changed from 24 to Rudder
- Category changed from Techniques to Techniques
Actions