Project

General

Profile

Actions
Copy link

Bug #7689

closed

Error on promise generation after accepting a node

Added by Nicolas CHARLES almost 9 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Web - Config management
Target version:
3.0.13
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On Rudder 3.2~rc1-3, I accept a node, and no promise generation happen
So I click on update, and I have a failure:
⇨ cf-promise check fails for promises generated at '/var/rudder/share/479d8ed6-38a7-4562-aee2-c7570f0e68f5/rules.new/cfengine-community'
⇨ Command to check generated promises is: '/var/rudder/cfengine-community/bin/cf-promises -f /var/rudder/share/479d8ed6-38a7-4562-aee2-c7570f0e68f5/rules.new/cfengine-community/promises.cf'
⇨ error: Can't stat file '/var/rudder/share/479d8ed6-38a7-4562-aee2-c7570f0e68f5/rules.new/cfengine-community/promises.cf' for parsing. (stat: No such file or directory)

Indeed, the generated policies don't contain the "common" system technique (but inventory is there)
Clearing the cache don't solve the issue, but reloading the dynamic group does correct the policy generation

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #7544: Accpeting several nodes *still* not accept them allReleasedVincent MEMBRÉ2015-12-04Actions
Related to Rudder - Bug #10446: Policy validation failsReleasedFrançois ARMANDActions
Actions
Copy link

Also available in: Atom PDF