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

Added by Nicolas CHARLES about 8 years ago. Updated over 1 year 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 PECCATTE2016-10-13Actions
Actions #1

Updated by Benoît PECCATTE about 8 years ago

  • 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

Actions #2

Updated by Alexis Mousset about 8 years ago

  • Target version changed from 321 to 4.0.1
Actions #3

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.0.1 to 4.0.2
Actions #4

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.0.2 to 4.0.3
Actions #5

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.0.3 to 4.0.4
Actions #6

Updated by Benoît PECCATTE over 7 years ago

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

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.4 to 4.0.5
Actions #8

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.5 to 4.0.6
  • Priority changed from 16 to 15
Actions #9

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.6 to 4.0.7
Actions #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.7 to 357
Actions #11

Updated by Benoît PECCATTE over 7 years ago

  • Priority changed from 15 to 29
Actions #12

Updated by Alexis Mousset over 7 years ago

  • Target version changed from 357 to 4.1.6
Actions #13

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.6 to 4.1.7
  • Priority changed from 29 to 28
Actions #14

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.7 to 4.1.8
Actions #15

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.8 to 4.1.9
  • Priority changed from 28 to 27
Actions #16

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #17

Updated by Vincent MEMBRÉ almost 7 years ago

  • Parent task deleted (#9351)
Actions #18

Updated by Vincent MEMBRÉ almost 7 years ago

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

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #20

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #21

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #22

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #23

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #24

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #25

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #26

Updated by Vincent MEMBRÉ almost 6 years ago

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

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions #28

Updated by Alexis Mousset almost 6 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions #29

Updated by François ARMAND over 5 years ago

  • Target version changed from 4.1.20 to 4.1.21
Actions #30

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.21 to 4.1.22
Actions #31

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.22 to 4.1.23
Actions #32

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.23 to 4.1.24
Actions #33

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.24 to 588
Actions #34

Updated by François ARMAND over 5 years ago

  • Target version changed from 588 to 5.0.13
Actions #35

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions #36

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions #37

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #38

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions #39

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #40

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions #41

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions #42

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.20 to 797
Actions #43

Updated by Benoît PECCATTE over 3 years ago

  • Target version changed from 797 to 6.1.14
Actions #44

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #45

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #46

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #47

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #48

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #49

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #50

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #51

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #52

Updated by Alexis Mousset almost 2 years ago

  • Target version changed from old 6.1 issues to relocate to old 6.2 issues to relocate
Actions #53

Updated by Nicolas CHARLES over 1 year ago

  • 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: Atom PDF