Project

General

Profile

Actions

Bug #9359

closed

Agent capabilities should be per agent, and not per node

Added by Nicolas CHARLES over 7 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
1
Category:
Agent
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

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 issues 4 (0 open4 closed)

Related to Rudder - Bug #9361: /usr/share/ncf/tree/30_generic_methods/file_from_template_jinja2.cf prevents Rudder to generate promises when CFEngine Enterprise is installedRejected2016-10-13Actions
Related to Rudder - Architecture #9384: Create a cfengine_rudder classReleasedBenoît PECCATTEActions
Related to Rudder - Architecture #9108: Add a capabilities files in rudder agent packageReleasedAlexis Mousset2016-09-14Actions
Related to Rudder - User story #12109: Agent capabilities in inventory are not parsedReleasedVincent MEMBRÉActions
Actions

Also available in: Atom PDF