Project

General

Profile

Bug #18172

Group query with OR composition and searching for Node properties return all nodes in place of none

Added by François ARMAND 18 days ago. Updated 9 days ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
94

Description

If you choose a search on a node property that should return 0 node, like "Name equals" and a name not used anywhere, you get ALL nodes in place of NONE.


Related issues

Related to Rudder - Bug #18133: Group query with OR composition and searching for Node properties return less results than expectedReleasedNicolas CHARLESActions
#1

Updated by François ARMAND 18 days ago

  • Related to Bug #18133: Group query with OR composition and searching for Node properties return less results than expected added
#2

Updated by François ARMAND 18 days ago

This can be reproduced with test:

    val q3 = TestQuery(
      "q3", // select no nodes because that property name doesn't exists
      parser(""" 
      { "select":"node", "composition" : "Or", "where":[
        { "objectType":"serializedNodeProperty", "attribute":"name.value", "comparator":"hasKey", "value":"No node with that prop" }
      ] }
      """).openOrThrowException("For tests"),
      Nil)
// fail: returns all nodes
#3

Updated by Vincent MEMBRÉ 18 days ago

  • Status changed from New to In progress
#4

Updated by Vincent MEMBRÉ 18 days ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/3205
#5

Updated by Vincent MEMBRÉ 18 days ago

  • Target version changed from 5.0.20 to 5.0.19
#6

Updated by Vincent MEMBRÉ 18 days ago

  • Status changed from In progress to Pending release
#8

Updated by Vincent MEMBRÉ 9 days 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.

Also available in: Atom PDF