Project

General

Profile

Bug #14379

Directive appear in "mixed" mode in a rule applied on only one node

Added by Nicolas CHARLES over 1 year ago. Updated 10 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
53

Description

I have a case where one rules shows 2 directives in mixed mode - even if it applies to one node (see screenshot)


Files

mixed.png (27.8 KB) mixed.png mixed on one rule Nicolas CHARLES, 2019-02-26 10:40
rules-on-multiple.png (38.3 KB) rules-on-multiple.png Nicolas CHARLES, 2019-02-26 10:43

Related issues

Related to Rudder - Bug #15125: Rule shown as "Mixed" whereas is is applied only to one audit nodeNewBenoît PECCATTEActions
#1

Updated by Nicolas CHARLES over 1 year ago

reason is : this directives are applied in another rule, with a mixed mode there
see screenshot

#2

Updated by Nicolas CHARLES over 1 year ago

  • Category set to Web - Compliance & node report
#3

Updated by François ARMAND over 1 year ago

  • Target version set to 4.1.21
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Priority changed from 0 to 70
#4

Updated by François ARMAND over 1 year ago

  • Assignee set to François ARMAND
  • Target version changed from 4.1.21 to 4.3.11
  • Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
  • User visibility changed from Getting started - demo | first install | Technique editor and level 1 Techniques to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 70 to 32

So, the problem only appears when a directive is used on two rule, and one of the rule dictates the mixed mode, but it does not make sens in the context of the other rule because that rule only apply to homogeneous nodes.

#5

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.3.11 to 4.3.12
#6

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.3.12 to 4.3.13
#7

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.3.13 to 4.3.14
#8

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.3.14 to 587
  • Priority changed from 32 to 31
#9

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 587 to 4.3.14
#10

Updated by Alexis MOUSSET about 1 year ago

  • Target version changed from 4.3.14 to 5.0.13
#11

Updated by Nicolas CHARLES about 1 year ago

  • Related to Bug #15125: Rule shown as "Mixed" whereas is is applied only to one audit node added
#12

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 31 to 30
#13

Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 30 to 29
#14

Updated by François ARMAND 10 months ago

  • Effort required set to Very Small
  • Priority changed from 29 to 54

We should spend a "very small" budget to see if we don't just missed a filter by node at some place.

#15

Updated by François ARMAND 10 months ago

  • Status changed from New to In progress
#16

Updated by François ARMAND 10 months ago

  • 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/2601
#17

Updated by François ARMAND 10 months ago

  • Status changed from Pending technical review to Pending release
#22

Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending release to Released
  • Priority changed from 54 to 53

This bug has been fixed in Rudder 5.0.15 which was released today.

Also available in: Atom PDF