Bug #13424
closed
Group of group is empty if we use the AND combinator
Added by Benoît PECCATTE almost 6 years ago.
Updated almost 6 years ago.
Category:
Web - Nodes & inventories
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Description
I have a Redhat group and a webserver group.
If I want to create a rehdat webserver group with 2 criteria the resulting group is empty
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Effort required set to Very Small
- Priority changed from 0 to 80
We should be at least capable to quickly add a test for it to better know the required effort.
- Target version changed from 4.3.5 to 4.3.6
- Assignee set to François ARMAND
- Status changed from New to In progress
The problem is that the request done looks like:
LDAPObjectType(groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration,Sub,LDAPObjectTypeFilter((objectClass=nodeGroup)),Some((&(nodeGroupId=test-group-node1)(nodeGroupId=test-group-node12))),NodeDnJoin,Set())
The "and" must be on the resulting list of nodes, not on the nodeGroupId.
Also: it's only on intersection of N groups. If you have a group and something else (for ex: a node by hostname), it works (because in that case, as the attribute are not the same, the and is done on nodes)
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2050
- Status changed from Pending technical review to Pending release
- Translation missing: en.field_tag_list set to Next minor release
- Priority changed from 80 to 79
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.6 and 5.0.2 which were released today.
Changelog
Changelog
Also available in: Atom
PDF