Actions
Bug #3564
closedThe 2.6 cf-lock erasing promise does not work on TokyoCabinet databases
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
The 2.6 cf-lock erasing promise does not work on TokyoCabinet databases
Updated by Matthieu CERDA over 11 years ago
- Pull Request changed from https://github.com/Normation/rudder-techniques/pull/112 to https://github.com/Normation/rudder-techniques/pull/116
PR updated
Updated by Matthieu CERDA over 11 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:96ec3865ba8595940a080c301725898346a6bc2d.
Updated by Jonathan CLARKE over 11 years ago
Applied in changeset commit:9b85959bcd07c41c30ee4f817d9b38d16ea02121.
Updated by François ARMAND over 11 years ago
Applied in changeset rudder:c9c3b0906e25f971017f271c2969b42f85be1e2e.
Updated by Vincent MEMBRÉ over 11 years ago
Applied in changeset rudder:0507b06fe652dfa93a4c30326a89d0ee0f163244.
Updated by Vincent MEMBRÉ over 11 years ago
commits rudder:c9c3b090 and rudder:0507b06f should be in issue #3565
Updated by Nicolas CHARLES over 11 years ago
Hum, on this one, I guess we should rather detect the CFEngine version currently used, and purge the appropriate database, rather than relying on the technique branch
There may be cases where people would have a mixed installation, with 2.5 / 2.6 agent server, and maybe having 2.5 technique on 2.6 agent.
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending release to Released
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 24 to Rudder
- Category changed from Techniques to Techniques
Actions