Project

General

Profile

Actions

Bug #3564

closed

The 2.6 cf-lock erasing promise does not work on TokyoCabinet databases

Added by Matthieu CERDA over 11 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Matthieu CERDA
Category:
Techniques
Target version:
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

Actions #1

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

Actions #2

Updated by Matthieu CERDA over 11 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:96ec3865ba8595940a080c301725898346a6bc2d.

Actions #3

Updated by Jonathan CLARKE over 11 years ago

Applied in changeset commit:9b85959bcd07c41c30ee4f817d9b38d16ea02121.

Actions #6

Updated by Vincent MEMBRÉ over 11 years ago

commits rudder:c9c3b090 and rudder:0507b06f should be in issue #3565

Actions #7

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.

Actions #8

Updated by Nicolas PERRON over 11 years ago

  • Status changed from Pending release to Released
Actions #9

Updated by Benoît PECCATTE almost 10 years ago

  • Project changed from 24 to Rudder
  • Category changed from Techniques to Techniques
Actions

Also available in: Atom PDF