Bug #18133
closedGroup query with OR composition and searching for Node properties return less results than expected
Description
When we do a query with OR composition, and at least a search criteria Node properties or Node State, the result show less results than expected.
in fact it show only the result that are the intersection of the node properties query and the other criterions
let say I have 3 Nodes, A, B, C, with C having a property 'query', and A and B belonging to group foo
if i create a group bar, with the composition OR, and criterion:- belonging to group foo
- having a property 'query'
I will have 0 Nodes that match, although I expect 3 nodes (A,B from first criteria, C from second)
if C was in group foo, i would have only C as a result
The bug is that when looking for node information, we don't use the composition operator defined between classic(inventory) criterion and node (NodeInfo) criterion, but use only && instead
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from New to In progress
Updated by Vincent MEMBRÉ over 4 years ago
- Subject changed from Group query with OR composition and searching for Node properties return less result than expected to Group query with OR composition and searching for Node properties return less results than expected
Updated by Vincent MEMBRÉ over 4 years ago
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/3187
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder|adeea67804d3bdd983599d997b9a93a95210c4d5.
Updated by François ARMAND over 4 years ago
- Related to Bug #18172: Group query with OR composition and searching for Node properties return all nodes in place of none added
Updated by François ARMAND over 4 years ago
- Fix check changed from To do to Error - Blocking
Correction broke the case where no nodes should be returned: now, all nodes are returned
Updated by Vincent MEMBRÉ over 4 years ago
- Fix check changed from Error - Blocking to Error - Fixed
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.19, 6.0.8 and 6.1.4 which were released today.