Bug #8792
closedTransient ncf error when updating from 3.1.10 to 3.1.12
Description
2016-07-29T10:07:28+0000 error: Can't stat file '/var/rudder/cfengine-community/inputs/10_ncf_internals/dispatcher.cf' for parsing. (stat: No such file or directory) 2016-07-29T10:07:28+0000 error: Policy failed validation with command '"/var/rudder/cfengine-community/bin/cf-promises" -c "/var/rudder/cfengine-community/inputs/promises.cf"' 2016-07-29T10:07:28+0000 error: CFEngine was not able to get confirmation of promises from cf-promises, so going to failsafe
Appeared during upgrade, linked to the update of promises/ncf.
Disappeared before the first run.
Updated by Nicolas CHARLES over 8 years ago
We changed the list-compatible-inputs script in #8559
Since the script needs one run to be updated, there is one run where promises call the old script with the new paramters, hence the transitory error message
Updated by Alexis Mousset over 8 years ago
- Status changed from New to Rejected
- Target version set to 3.1.16
We changed the output of list-compatible-inputs in #8553/#8559 to output only the relative path to ncf folder. When using old promises.cf with a new ncf (before first generation after upgrade), we try to load the relative path, which CFEngine understands as relative to the inputs dir, hence the given result.
As it is a transient error that disappears at the end of the upgrade process, and linked to the upgrade order between ncf and Rudder, closing.