Forum: CFEngine Help
Subject: CFEngine 3.2.0 - only my thoughts
Author: schattenfell
Link to topic: https://cfengine.com/forum/read.php?3,23223,23223#msg-23223
Hello,
at first thanks to the CFEngine team for the new 3.2.0 release. Good job,
especially to dottedmag who solved a lot of bug reports.
Well, we just upgraded our CFEngine 3.1.5 to 3.2.0 under Debian Squeeze 64 Bit
because we were affected by some of the patched problems.
We got in trouble with some of our rules:
In CFEngine 3.1.5 it was possible to make e.g. file promises like this, without
any error:
files:
"/temp/testfile.txt"
create => "true",
perms => file("root", "root", "0660"),
edit_defaults => empty_file,
edit_line => add_line("test_content"),
promise_repaired => { "testfile_updated" };
In CFEngine 3.2.0 we get "Constraint lvalue 'promise_repaired' is not allowed
in bundle category 'files', near token '}'".
So I looked up in the manual and found out that I always have to use the
classes ext body template and it was my luck that I could use it till now
without any error message: problem solved. So this was apparently a fix, that
was not documented in CFEngine 3.2.0 changelog. It would be nice, if any change
in new releases would be mentionned, even if there was no bugreport about it.
Secondly we are surprised about the new behaviour of the require_comments menu
option. We use:
require_comments => "true";
We use comments for all our promises and in CFEngine 3.1.5 we got no errors.
In CFEngine 3.2.0 suddenly also class definitions seems to be handled as
promises for this option, example:
bundle common c
{
classes:
"Test_Class_Server" expression => "name_of_server";
}
We now get errors like this: "Promise (version 1.0) belongs to bundle 'c' in
file '[...]' near line [...] !! Un-commented promise found, but comments have
been required by policy". Adding comments solved the problem.
Is this the expected behaviour by design? It looks like a bug introduced in
CFEngine 3.2.0.
Best wishes
Michael
_______________________________________________
Help-cfengine mailing list
[email protected]
https://cfengine.org/mailman/listinfo/help-cfengine
