Project

General

Profile

Bug #13772

Network group criteria not working

Added by Benoît PECCATTE about 1 month ago. Updated 17 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 | level 1 Techniques
Effort required:
Very Small
Priority:
0

Description

Gateway criterium:
  • Network interfaces > Gateway > Regex > .*192.168.* -> no match (there should be 15)
  • Network interfaces > Gateway > 1s defined -> 1 match (there should be 15)
Network address criterium:
  • Network interfaces > Network > Regex > .*192.168.* -> 6 matches (there should be 27)
  • Network interfaces > Network > Is defined -> 6 matches (there should be 27)
Netmask criterium:
  • Network interfaces > Mask > Regex > .*192.168.* -> 6 matches (there should be 27)
  • Network interfaces > Mask > Is defined -> 6 matches (there should be 27)

IP address:

  • Network interfaces > IP address > Regex > ^$ -> no match (there should be at least 10)

Subtasks

Bug #13815: Test failing after fix on network node queriesReleasedFrançois ARMAND

Related issues

Related to Rudder - Bug #13807: Fusion does not parse network gateway correctlyNew

Associated revisions

Revision 3186da78 (diff)
Added by François ARMAND about 1 month ago

Fixes #13772: Network group criteria not working

History

#1 Updated by François ARMAND about 1 month ago

  • Category set to Web - Nodes & inventories
  • Target version set to 4.1.17
  • Effort required set to Very Small

It should be easy to add test and check for these problems.

#2 Updated by François ARMAND about 1 month ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 122

#3 Updated by François ARMAND about 1 month ago

  • Priority changed from 122 to 0

#4 Updated by François ARMAND about 1 month ago

  • Status changed from New to Rejected

So, there is several problems here, but none related to research exactly:

- Gateway, network, mask values are not correctly parsed/added (which is hard to tell because the info are missing in UI o_O) => new tickets #13803 #13804
- there is a difference between "matches regex ^$" (ie empty string) and "the value is missing" => need to user "is not defined" for the latter one.

I'm not sure what we can do for that last elements.

I'm closing that one.

#5 Updated by François ARMAND about 1 month ago

  • Status changed from Rejected to In progress

In fact, I'm still going to add some test to validate that.

#6 Updated by François ARMAND about 1 month ago

  • Status changed from In progress to Pending technical review
  • Assignee set to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/2056

#7 Updated by Normation Quality Assistant about 1 month ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND

#8 Updated by François ARMAND about 1 month ago

  • Related to Bug #13807: Fusion does not parse network gateway correctly added

#9 Updated by François ARMAND about 1 month ago

  • Status changed from Pending technical review to Pending release

#10 Updated by Vincent MEMBRÉ 17 days ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.17, 4.3.7 and 5.0.3 which were released today.
Changelog
Changelog
Changelog

Also available in: Atom PDF