Actions
Bug #3570
closedCFEngine 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
Actions