Actions
Bug #8710
closedCannot read ncf inputs due to duplicated path
Bug #8710:
Cannot read ncf inputs due to duplicated path
Status:
Rejected
Priority:
N/A
Assignee:
Category:
System techniques
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Path for inputs on master are prefixed two times by "/var/Rudder/ncf", which does not exists
root@server:~# rudder agent run -i Rudder agent 3.2.4-jessie0 (CFEngine Core 3.7.1) Node uuid: root error: Can't stat file '/var/rudder/ncf//var/rudder/ncf/common/10_ncf_internals/expand_configuration.cf' for parsing. (stat: No such file or directory) error: Policy failed validation with command '"/var/rudder/cfengine-community/bin/cf-promises" -c "/var/rudder/cfengine-community/inputs/promises.cf"' error: CFEngine was not able to get confirmation of promises from cf-promises, so going to failsafe
Remove ${ncf_path} when listing inputs, fixes the issue (like here in https://github.com/Normation/rudder-techniques/blob/master/techniques/system/common/1.0/promises.st#L138 )
Updated by François ARMAND about 10 years ago
- Translation missing: en.field_tag_list set to Blocking 4.0
Updated by Alexis Mousset about 10 years ago
This looks like the other side of #8792, when ncf is upgraded first, before the promise.cf.
Updated by Alexis Mousset about 10 years ago
- Related to Bug #8792: Transient ncf error when updating from 3.1.10 to 3.1.12 added
Updated by Alexis Mousset about 10 years ago
If we can confirm it disappears after first generation, we can close as duplicate of #9207.
Updated by Alexis Mousset about 10 years ago
- Related to Architecture #9207: Transient policy error after upgrade, need to improve handling of policies update during server upgrade (rudder-upgrade vs. ncf vs. rudder-techniques) added
Updated by Nicolas CHARLES about 10 years ago
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
I'm investigating the issue.
A fresh install doesn't have the issue, trying to upgrade to check if it happens
Updated by Nicolas CHARLES about 10 years ago
- Status changed from New to Rejected
i cannot reproduce this anymore, from scratch nor upgrade from 3.2 to 4.0
I'm rejecting this ticket
Actions