Project

General

Profile

Actions

Bug #21924

closed

Policy generation broken when defining a group with invert result of inclusion of another group

Added by Nicolas CHARLES over 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
It bothers me each time
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
111
Name check:
To do
Fix check:
Checked
Regression:
No

Description

I created this group

and policy generation broke
No properties are definied by these groups (but an update campain is defined on the passiv group)

Error is

[2022-10-06 16:46:53+0200] ERROR policy.generation - Error while building target configuration node for node 'c8e2c037-78df-4530-8f3a-db7d337517c9' which is one of the target of rules.
 Ignoring it for the rest of the process <- Inconsistency: Error when looking for parent group '57e9a28c-8e0c-41f1-b7fa-2847c19f35d4' of group 'Active group' [191510ea-c276-4e19-9c34-3
ba03dc49587]. Please check criterium for that group.

happen in 7.2, maybe in earlier versions

Workaround: you can implement that behavior as rule site in place of at group site, by having in the include part of the rule "all nodes" and in the exclude part of the rule the group which was in the group criteria inverted.

analysis: the error is during node properties resolution. The code says "I don't find the group in the property hierarchy for which we told to NOT look for (invert). So in that case, we should just say "that group does not take part of property inheritance".


Files

clipboard-202210061648-jbog1.png (30.6 KB) clipboard-202210061648-jbog1.png Nicolas CHARLES, 2022-10-06 16:48
Actions

Also available in: Atom PDF