CFEngine defects are managed in our [bug tracker][bug tracker]. Please report bugs or unexpected behavior there, following the documented guideline for new bug reports.
The items below highlight issues that require additional awareness when starting with CFEngine or when upgrading from a previous version.
https://dev.cfengine.com/issues/1492
cf-promises --show-classes and cf-promises --show-vars will only show
classes and variables found on a first pass through the policy, since
cf-promises does not evaluate agent promises.
The CFEngine protocol versions 1 and 2 are incompatible (the latter is based on TLS). CFEngine 3.6 supports both protocol versions, but earlier versions only support protocol version 1. Protocol version 1 is still the default in 3.6 but the default will change to 2 in future versions.
Installing the Community Edition gives the following message, but it should be silent:
Starting cfengine3 (via systemctl): [ OK ]
Starting the CFEngine daemons from policy, e.g. bootstrapping, does not make systemd aware that CFEngine is running. Thus, using systemd while removing the rpm, starting, stopping CFEngine is not handled correctly.
ps and kill tools directly using [commands promises][commands].edit_xml bundles][bundle edit_xml] do not work on HP-UX.There is currently no setting in Mission Portal to configure the sender email address. This issue is on the backlog and will be addressed in a future release.
To change the setting you must edit the from email address in
/var/cfengine/httpd/htdocs/application/config/appsettings.php
// Default FROM email address
$config['appemail'] = 'admin@organisation.com';