Project

General

Profile

Actions

Bug #9521

closed

If we are in non-compliance only report mode, we don't get the wrong mode error message, and node in is "no answer" in the interface

Bug #9521: If we are in non-compliance only report mode, we don't get the wrong mode error message, and node in is "no answer" in the interface

Added by Nicolas CHARLES about 9 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
1 (highest)
Assignee:
-
Category:
System techniques
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
No

Description

In "non compliance only" report mode, everything that is not error or repaired is filtered out
but the abort message is a log_info, so it isn't created, so the node stays in no answer


Related issues 1 (0 open1 closed)

Related to Rudder - User story #9351: Create a dedicated abort report when enforce is used in place of auditReleasedBenoît PECCATTEActions

Updated by Benoît PECCATTE about 9 years ago Actions #1

  • Translation missing: en.field_tag_list deleted (Blocking 4.0)
  • Description updated (diff)
  • Target version changed from 4.0.0~rc3 to 321

This is tied to the way we managed those messages. They are of a log_info type.
If we want this to be general this must be changed.

So the goal is :
- change log_info to something yet to be decided (like out_of_band, ...)
- always transmit this type (event in change only)
- process this type in the server
- migrate start and stop messages to this new type

Updated by Alexis Mousset about 9 years ago Actions #2

  • Target version changed from 321 to 4.0.1

Updated by Vincent MEMBRÉ about 9 years ago Actions #3

  • Target version changed from 4.0.1 to 4.0.2

Updated by Vincent MEMBRÉ about 9 years ago Actions #4

  • Target version changed from 4.0.2 to 4.0.3

Updated by Vincent MEMBRÉ almost 9 years ago Actions #5

  • Target version changed from 4.0.3 to 4.0.4

Updated by Benoît PECCATTE over 8 years ago Actions #6

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority set to 16

Updated by Vincent MEMBRÉ over 8 years ago Actions #7

  • Target version changed from 4.0.4 to 4.0.5

Updated by Vincent MEMBRÉ over 8 years ago Actions #8

  • Target version changed from 4.0.5 to 4.0.6
  • Priority changed from 16 to 15

Updated by Vincent MEMBRÉ over 8 years ago Actions #9

  • Target version changed from 4.0.6 to 4.0.7

Updated by Vincent MEMBRÉ over 8 years ago Actions #10

  • Target version changed from 4.0.7 to 357

Updated by Benoît PECCATTE over 8 years ago Actions #11

  • Priority changed from 15 to 29

Updated by Alexis Mousset over 8 years ago Actions #12

  • Target version changed from 357 to 4.1.6

Updated by Vincent MEMBRÉ over 8 years ago Actions #13

  • Target version changed from 4.1.6 to 4.1.7
  • Priority changed from 29 to 28

Updated by Vincent MEMBRÉ over 8 years ago Actions #14

  • Target version changed from 4.1.7 to 4.1.8

Updated by Vincent MEMBRÉ about 8 years ago Actions #15

  • Target version changed from 4.1.8 to 4.1.9
  • Priority changed from 28 to 27

Updated by Vincent MEMBRÉ about 8 years ago Actions #16

  • Target version changed from 4.1.9 to 4.1.10

Updated by Vincent MEMBRÉ almost 8 years ago Actions #17

  • Parent task deleted (#9351)

Updated by Vincent MEMBRÉ almost 8 years ago Actions #18

  • Related to User story #9351: Create a dedicated abort report when enforce is used in place of audit added

Updated by Vincent MEMBRÉ almost 8 years ago Actions #19

  • Target version changed from 4.1.10 to 4.1.11

Updated by Vincent MEMBRÉ over 7 years ago Actions #20

  • Target version changed from 4.1.11 to 4.1.12

Updated by Vincent MEMBRÉ over 7 years ago Actions #21

  • Target version changed from 4.1.12 to 4.1.13

Updated by Vincent MEMBRÉ over 7 years ago Actions #22

  • Target version changed from 4.1.13 to 4.1.14

Updated by Benoît PECCATTE over 7 years ago Actions #23

  • Target version changed from 4.1.14 to 4.1.15

Updated by Vincent MEMBRÉ about 7 years ago Actions #24

  • Target version changed from 4.1.15 to 4.1.16

Updated by Vincent MEMBRÉ about 7 years ago Actions #25

  • Target version changed from 4.1.16 to 4.1.17

Updated by Vincent MEMBRÉ about 7 years ago Actions #26

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 27 to 0

Updated by Vincent MEMBRÉ almost 7 years ago Actions #27

  • Target version changed from 4.1.18 to 4.1.19

Updated by Alexis Mousset almost 7 years ago Actions #28

  • Target version changed from 4.1.19 to 4.1.20

Updated by François ARMAND almost 7 years ago Actions #29

  • Target version changed from 4.1.20 to 4.1.21

Updated by Vincent MEMBRÉ over 6 years ago Actions #30

  • Target version changed from 4.1.21 to 4.1.22

Updated by Vincent MEMBRÉ over 6 years ago Actions #31

  • Target version changed from 4.1.22 to 4.1.23

Updated by Vincent MEMBRÉ over 6 years ago Actions #32

  • Target version changed from 4.1.23 to 4.1.24

Updated by Vincent MEMBRÉ over 6 years ago Actions #33

  • Target version changed from 4.1.24 to 588

Updated by François ARMAND over 6 years ago Actions #34

  • Target version changed from 588 to 5.0.13

Updated by Vincent MEMBRÉ over 6 years ago Actions #35

  • Target version changed from 5.0.13 to 5.0.14

Updated by Vincent MEMBRÉ about 6 years ago Actions #36

  • Target version changed from 5.0.14 to 5.0.15

Updated by Vincent MEMBRÉ about 6 years ago Actions #37

  • Target version changed from 5.0.15 to 5.0.16

Updated by Alexis Mousset almost 6 years ago Actions #38

  • Target version changed from 5.0.16 to 5.0.17

Updated by Vincent MEMBRÉ over 5 years ago Actions #39

  • Target version changed from 5.0.17 to 5.0.18

Updated by Vincent MEMBRÉ over 5 years ago Actions #40

  • Target version changed from 5.0.18 to 5.0.19

Updated by Vincent MEMBRÉ over 5 years ago Actions #41

  • Target version changed from 5.0.19 to 5.0.20

Updated by Vincent MEMBRÉ about 5 years ago Actions #42

  • Target version changed from 5.0.20 to 797

Updated by Benoît PECCATTE over 4 years ago Actions #43

  • Target version changed from 797 to 6.1.14

Updated by Vincent MEMBRÉ over 4 years ago Actions #44

  • Target version changed from 6.1.14 to 6.1.15

Updated by Vincent MEMBRÉ over 4 years ago Actions #45

  • Target version changed from 6.1.15 to 6.1.16

Updated by Vincent MEMBRÉ over 4 years ago Actions #46

  • Target version changed from 6.1.16 to 6.1.17

Updated by Vincent MEMBRÉ about 4 years ago Actions #47

  • Target version changed from 6.1.17 to 6.1.18

Updated by Vincent MEMBRÉ about 4 years ago Actions #48

  • Target version changed from 6.1.18 to 6.1.19

Updated by Vincent MEMBRÉ over 3 years ago Actions #49

  • Target version changed from 6.1.19 to 6.1.20

Updated by Vincent MEMBRÉ over 3 years ago Actions #50

  • Target version changed from 6.1.20 to 6.1.21

Updated by Vincent MEMBRÉ over 3 years ago Actions #51

  • Target version changed from 6.1.21 to old 6.1 issues to relocate

Updated by Alexis Mousset almost 3 years ago Actions #52

  • Target version changed from old 6.1 issues to relocate to old 6.2 issues to relocate

Updated by Nicolas CHARLES over 2 years ago Actions #53

  • Status changed from New to Rejected
  • Regression set to No

we worked on that, and it doesn't seem to happen anymore

Actions

Also available in: PDF Atom