-
Notifications
You must be signed in to change notification settings - Fork 188
BugReport
Please test whether the bug you are encountering is reproducible with development version of CFEngine. In order to do Build the development version and see whether the bug still persists.
If the bug has been fixed, you may still open a bugreport, and ask for a bugfix to be put into a next patch release. Note that we only issue patch releases for latest released minor/major release, so no patch releases will be made for (for example) 3.0.x series if 3.1.0 is already released.
If the bug seems to be still present (and it is not a crash or another obvious defect), please check with community members (using IRC or mailing list) whether the observed behaviour is indended one.
Please gather information about the problem: version of CFEngine (generally it should be a HEAD of git repository, as the bug should be reproducible in the development version), operating system, CPU architecture, any traces as described on Troubleshooting page, and logs produced by CFEngine.
If the bug is triggered by a particular policy, please trim down the policy to produce a "minimal example". Even better if you can turn it into an [[acceptance test|https://github.com/cfengine/core/blob/master/tests/acceptance/README]]. Minimal examples are generally added to testsuite for regression testing.
Open a new issue in bug tracker, describe the problem, and attach all the gathered information.