User story #12109
closed
Agent capabilities in inventory are not parsed
Added by François ARMAND almost 7 years ago.
Updated over 4 years ago.
Category:
Web - Nodes & inventories
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Description
Agent capabilities from inventory (see #9151) are not parsed and store in node info.
Moreover, it is said in #9359 that agent capabilities should be per-agent, not per-node, but the current inventory structure is:
<RUDDER>
<AGENT>
<AGENT_NAME>cfengine-community</AGENT_NAME>
....
</AGENT>
<AGENT_CAPABILITIES>
<AGENT_CAPABILITY>cfengine</AGENT_CAPABILITY>
....
</AGENT_CAPABILITIES>
So we also certainly need to update how inventory is done.
I'm setting the target to 4.1 because we need LTS agent to report the correct things, but perhaps that the parsing/save in node can be done in a next major release.
- Related to Bug #9359: Agent capabilities should be per agent, and not per node added
- Target version changed from 4.1.10 to 4.1.11
- Target version changed from 4.1.11 to 4.1.12
- Target version changed from 4.1.12 to 4.1.13
- Target version changed from 4.1.13 to 411
- Target version changed from 411 to 4.1.13
- Target version changed from 4.1.13 to 4.1.14
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 48
- Target version changed from 4.1.14 to 4.1.15
- Target version changed from 4.1.15 to 4.1.16
- Priority changed from 48 to 46
- Target version changed from 4.1.16 to 4.1.17
- Priority changed from 46 to 45
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 45 to 0
- Target version changed from 4.1.18 to 4.1.19
- Target version changed from 4.1.19 to 4.1.20
- Target version changed from 4.1.20 to 4.1.21
- Target version changed from 4.1.21 to 4.1.22
- Target version changed from 4.1.22 to 4.1.23
- Target version changed from 4.1.23 to 4.1.24
- Target version changed from 4.1.24 to 588
- Target version changed from 588 to 5.0.13
- Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
We do not have multi-agent use cases any more, and capabilities are currently not used, so it is not really important at the moment, but still nice to have.
Setting to minor.
- Target version changed from 5.0.13 to 5.0.14
- Target version changed from 5.0.14 to 5.0.15
- Status changed from New to Rejected
We don't use capabilities anymore. We won't remove them from inventory for now, but we won't parse that field (or not like that) server side.
- Status changed from Rejected to In progress
- Target version changed from 5.0.15 to 6.1.0~beta1
It happens that capabilities are important sometimes, so it would be nice to have.
- Assignee set to François ARMAND
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2880
- Status changed from Pending technical review to Pending release
- Tracker changed from Bug to User story
- Severity deleted (
Minor - inconvenience | misleading | easy workaround)
- Priority deleted (
0)
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.0~beta1 which was released today.
Also available in: Atom
PDF