Project

General

Profile

Actions
Copy link

Bug #17653

closed

when a node is just accepted, on the node list there a warning sign that the system policy could not be applied

Bug #17653: when a node is just accepted, on the node list there a warning sign that the system policy could not be applied

Added by Nicolas CHARLES almost 6 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
Elaad FURREEDAN
Category:
Web - Compliance & node report
Target version:
6.1.19
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
55
Name check:
To do
Fix check:
To do
Regression:

Description

this message should only happen after the grace period

Related issues 1 (1 open — 0 closed)

Is duplicate of Rudder - Bug #8761: New nodes have compliance warning for system technique just after being addedNewActions

Updated by Vincent MEMBRÉ almost 6 years ago Actions
Copy link
 #1

  • Target version changed from 6.1.0~rc3 to 6.1.0~rc4

Updated by Vincent MEMBRÉ almost 6 years ago Actions
Copy link
 #3

  • Target version changed from 6.1.0~rc4 to 6.1.0

Updated by Vincent MEMBRÉ almost 6 years ago Actions
Copy link
 #4

  • Target version changed from 6.1.0 to 6.1.1

Updated by François ARMAND almost 6 years ago Actions
Copy link
 #6

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Effort required set to Small
  • Priority changed from 0 to 66

I think it's because just after acceptation, there's no configuration at all for that node (generation not finished), so the compliance doesn't know it is in grace period yet.

We could have a special case that checks for acceptation time if there is no config yet, and set to "pending" in that case.

Updated by Nicolas CHARLES almost 6 years ago Actions
Copy link
 #7

policy generation was done, but reports were not received

Updated by François ARMAND almost 6 years ago Actions
Copy link
 #8

Elaad, when you will be working on that one, the first steps will be:

- add a log like that:

  <logger name="explain_compliance.node_uuid_that_will_be_accepted" level="trace"/>

- reproduce the problem,
- add screenshot of the message explanation message node details compliance tab, and add logs here.

If you get stuck when trying to understand the problem, ask for help.

Updated by François ARMAND almost 6 years ago Actions
Copy link
 #9

  • Assignee set to Elaad FURREEDAN

Updated by Vincent MEMBRÉ almost 6 years ago Actions
Copy link
 #11

  • Target version changed from 6.1.1 to 6.1.2

Updated by Vincent MEMBRÉ almost 6 years ago Actions
Copy link
 #12

  • Target version changed from 6.1.2 to 6.1.3
  • Priority changed from 66 to 65

Updated by François ARMAND almost 6 years ago Actions
Copy link
 #13

  • Target version changed from 6.1.3 to 6.1.4

Updated by Elaad FURREEDAN over 5 years ago Actions
Copy link
 #14

  • Status changed from New to In progress
  • Priority changed from 65 to 64

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #15

  • Target version changed from 6.1.4 to 6.1.5

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #16

  • Target version changed from 6.1.5 to 6.1.6
  • Priority changed from 64 to 63

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #17

  • Target version changed from 6.1.6 to 6.1.7
  • Priority changed from 63 to 62

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #18

  • Target version changed from 6.1.7 to 6.1.8
  • Priority changed from 62 to 61

Updated by Elaad FURREEDAN over 5 years ago Actions
Copy link
 #19

  • Status changed from In progress to New

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #20

  • Target version changed from 6.1.8 to 6.1.9
  • Priority changed from 61 to 59

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #21

  • Target version changed from 6.1.9 to 6.1.10

Updated by Vincent MEMBRÉ about 5 years ago Actions
Copy link
 #22

  • Target version changed from 6.1.10 to 6.1.11
  • Priority changed from 59 to 58

Updated by Vincent MEMBRÉ about 5 years ago Actions
Copy link
 #23

  • Target version changed from 6.1.11 to 6.1.12

Updated by Vincent MEMBRÉ about 5 years ago Actions
Copy link
 #24

  • Target version changed from 6.1.12 to 6.1.13
  • Priority changed from 58 to 57

Updated by Vincent MEMBRÉ about 5 years ago Actions
Copy link
 #25

  • Target version changed from 6.1.13 to 6.1.14
  • Priority changed from 57 to 56

Updated by Vincent MEMBRÉ almost 5 years ago Actions
Copy link
 #26

  • Target version changed from 6.1.14 to 6.1.15
  • Priority changed from 56 to 55

Updated by Vincent MEMBRÉ almost 5 years ago Actions
Copy link
 #27

  • Target version changed from 6.1.15 to 6.1.16

Updated by Vincent MEMBRÉ over 4 years ago Actions
Copy link
 #28

  • Target version changed from 6.1.16 to 6.1.17

Updated by Vincent MEMBRÉ over 4 years ago Actions
Copy link
 #29

  • Target version changed from 6.1.17 to 6.1.18

Updated by Vincent MEMBRÉ over 4 years ago Actions
Copy link
 #30

  • Target version changed from 6.1.18 to 6.1.19

Updated by François ARMAND over 4 years ago Actions
Copy link
 #31

  • Is duplicate of Bug #8761: New nodes have compliance warning for system technique just after being added added

Updated by François ARMAND over 4 years ago Actions
Copy link
 #32

  • Status changed from New to Rejected

Closing as duplicate of #8761

Actions
Copy link

Also available in: PDF Atom