Bug #11183
closed
Group "All nodes known by Rudder directly connected to the XXXX server" excludes DSC nodes
Added by Nicolas CHARLES over 7 years ago.
Updated about 7 years ago.
Category:
Web - Nodes & inventories
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Description
DSC nodes are excluded from groups "all nodes known by rudder..." which is a pity :(
- Related to Bug #11171: Error when trying to remove a node added
- Target version changed from 4.2.0~beta3 to 4.2.0~rc1
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Effort required set to Very Small
- Priority changed from 0 to 49
- Assignee set to Vincent MEMBRÉ
There is a "all cfengine nodes" target in 4.2 that should be used in place of that one.
The bootstrap migration trigger must be updated, to.
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1733
So, we chose to only update the definition, stating that only CFEngine nodes are targeted, and that that group should not be use to configure user rules.
A more general purpose user group can be defined by hand with "node summary -> node policy ID -> = [ ]"
In the long term, the system group is expected to be removed.
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.2.0~rc1 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by