Bug #9359
closed
Agent capabilities should be per agent, and not per node
Added by Nicolas CHARLES about 8 years ago.
Updated over 2 years ago.
Severity:
Minor - inconvenience | misleading | easy workaround
Description
Agent capabilities should be per agent, rather than system global.
For instance, if you have a Rudder server with Rudder agent + Enterprise agent, the Rudder Agent has capabilities that Enterprise agent doesn't
So, as a result, the promises run with Enterprise fail (like dumpdatastate), and break the promise generation
- Related to Bug #9361: /usr/share/ncf/tree/30_generic_methods/file_from_template_jinja2.cf prevents Rudder to generate promises when CFEngine Enterprise is installed added
Arrg !
It should probably.
However, we try to support the main cfengine directly without modification. Which means that an enterprise version of the cfengine agent should never have capabilities.
So the solution could be to just ignore the capabilities file when we are running on a nova agent.
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1058
- Translation missing: en.field_tag_list changed from Sponsored to Sponsored, Blocking 4.0
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.1 and 3.2.10 which were released today.
Transient errors may remain during upgrade.
In the policies, ncf generic methods are loaded through /var/rudder/ncf/common/10_ncf_internals/list-compatible-inputs script
When Rudder and ncf is upgraded, ncf and Rudder Techniques are updated using different methods:
- Rudder Techniques are generated by the Web Interface, post installation
- ncf files are updated by packaging in /usr/share/ncf/, and copied by agent run to /var/rudder/ncf
Only when the agent is run does the list-compatible-inputs file is updated, so there may be a temporary de-synchronisation between Rudder policies and ncf, causing the error to be still present during upgrade. Symptom may be a red cross during policy generation in the Web Interface
To prevent issues, you can:
- upgrade Rudder and ncf
- (optionally) upgrade Rudder Techniques
- run "rudder agent update && rudder agent run" on the Rudder server
- log in the Web Interface - if policy generation shows a red cross, click on "Regenerate policies", which will solve the issue
David just told me this issue still happens
- Translation missing: en.field_tag_list changed from Sponsored, Blocking 4.0 to Sponsored
- Severity set to Minor - inconvenience | misleading | easy workaround
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by