Project

General

Profile

Actions
Copy link

Bug #24883

open

After upgrading to 8.1.2, nodes with no answer started to show as compliant

Added by Nicolas CHARLES 7 months ago. Updated 20 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
8.1.11
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

I have upgraded Rudder to 8.1.2, some nodes were offline for a long time
I got the following reporting output 

The latest reports received for this node are from a run started at 2024-03-25 13:10:56+0000

(nearly 2 months old

I tried to trigger a policy generation, and got this output (mostly the same)

Compliance seems to not be correctly initialized
Happen in 8.1, may happen in 8.0

Files

Download all files
clipboard-202405201720-ucmok.png (94.9 KB) clipboard-202405201720-ucmok.png Nicolas CHARLES, 2024-05-20 17:20
clipboard-202405201720-wjuuu.png (104 KB) clipboard-202405201720-wjuuu.png Nicolas CHARLES, 2024-05-20 17:20
Actions
Copy link
 #1

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 8.1.3 to 8.1.4
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.1.4 to 8.1.5
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.1.5 to 8.1.6
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.6 to 8.1.7
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.7 to 8.1.8
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 8.1.8 to 8.1.9
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ 25 days ago

  • Target version changed from 8.1.9 to 8.1.10
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ 20 days ago

  • Target version changed from 8.1.10 to 8.1.11
Actions
Copy link

Also available in: Atom PDF