Bug #2343
Cfengine Community 3.5 doesn't exist yet, so the compatibility of the techniques are not correct
| Status: | Released | Start date: | 2012-02-28 | |
|---|---|---|---|---|
| Priority: | 2 | Due date: | ||
| Assignee: |  Nicolas CHARLES |
% Done: | 100% |
|
| Category: | Techniques - Others | |||
| Target version: | 2.3.7 | |||
| Needs translating: | No | Pull Request: |
Description
Most Techniques state compatibility with Cfengine Community 3.5, which doesn't exist yet. Most of the time, it means 3.1.5
Associated revisions
Fixes #2343 : correct the version of cfengine in the requierement
Fixes #2343 : correct the version of cfengine in the requierement
(cherry picked from commit f5e924930e7a185d4536c7b434dd829fe2736766)
Signed-off-by: Jonathan Clarke <jonathan.clarke@normation.com>
Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
- branches/rudder/2.3:
Fixes #2454: The jobScheduler PT is now completely multivaluation compliant (reports and policy.xml adjusted)
Fixes #2470: Added the binary comparison method in copyGitFile that was missing, and corrected the configuration statement description
Fix reporting for post-hook in PT fileManagement. Fixes #2481
Refs #2465: Added a MAYBEEMPTY var on checkGenericFileContent to make the file content part optionnal
Fixes #2465: Adjusted checkGenericFileContent reports because of an extra report that should not be here
Fixes #2467 : allowing to create a group and edit it in the same run
Fixes #2465: The does not have a mandatory field to enforce file content anymore
Fixes #2258: remove deprecated <MULTIVALUED> tag for inputs in common/policy.xml (cherry picked from commit fc82b4d725ce4e3fde4bfe9e7a017547460a046c)
Fixes #2258: add missing section declaration around multivalued variables in common/policy.xml (cherry picked from commit 7f4a95fd1854cb27617c8d6887e7b09f7d5844a5)
Fixes #2343 : correct the version of cfengine in the requierement (cherry picked from commit f5e924930e7a185d4536c7b434dd829fe2736766)
Refs #2435 Change success report condition in aptPackageManagerSettings
TRIVIAL: Adding comments on reporting in aptPackageManagerSettings
Fixes #2467 : correct the reporting in the PT Group Management
Conflicts:
techniques/systemSettings/userManagement/groupManagement/1.0/groupManagement.st
Merge branch 'branches/rudder/2.4'
- branches/rudder/2.4:
Refs #2465 Change path and policy references in order to be 2.4+ compliant
Fixes #2454: The jobScheduler PT is now completely multivaluation compliant (reports and policy.xml adjusted)
Fixes #2470: Added the binary comparison method in copyGitFile that was missing, and corrected the configuration statement description
Fix reporting for post-hook in PT fileManagement. Fixes #2481
Refs #2465: Added a MAYBEEMPTY var on checkGenericFileContent to make the file content part optionnal
Fixes #2465: Adjusted checkGenericFileContent reports because of an extra report that should not be here
Fixes #2467 : allowing to create a group and edit it in the same run
Fixes #2465: The does not have a mandatory field to enforce file content anymore
Fixes #2258: remove deprecated <MULTIVALUED> tag for inputs in common/policy.xml (cherry picked from commit fc82b4d725ce4e3fde4bfe9e7a017547460a046c)
Fixes #2258: add missing section declaration around multivalued variables in common/policy.xml (cherry picked from commit 7f4a95fd1854cb27617c8d6887e7b09f7d5844a5)
Fixes #2343 : correct the version of cfengine in the requierement (cherry picked from commit f5e924930e7a185d4536c7b434dd829fe2736766)
Refs #2435 Change success report condition in aptPackageManagerSettings
TRIVIAL: Adding comments on reporting in aptPackageManagerSettings
Fixes #2467 : correct the reporting in the PT Group Management
History
#1
Updated by Nicolas CHARLES about 1 year ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:f5e924930e7a185d4536c7b434dd829fe2736766.
#2
Updated by Jonathan CLARKE about 1 year ago
- Status changed from Pending technical review to Released
- Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7
#3
Updated by Jonathan CLARKE about 1 year ago
- Target version changed from 2.4.0~alpha7 to 2.3.7
This was also the case on the 2.3 branch so I've backported the fix and modified the target version of this ticket in consequence.