Bug #13772: Network group criteria not working - Rudder - Issue Tracker

Actions

Copy link

Bug #13772

closed

Network group criteria not working

Added by Benoît PECCATTE about 6 years ago. Updated about 6 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - Nodes & inventories

Target version:

4.1.17

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Critical - prevents main use of Rudder | no workaround | data loss | security

UX impact:

User visibility:

Getting started - demo | first install | level 1 Techniques

Effort required:

Very Small

Priority:

Name check:

Fix check:

Regression:

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 1 (0 open — 1 closed)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by François ARMAND about 6 years 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.

Actions

Copy link

Updated by François ARMAND about 6 years 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

Actions

Copy link

Updated by François ARMAND about 6 years ago

Priority changed from 122 to 0

Actions

Copy link

Updated by François ARMAND about 6 years 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.

Actions

Copy link