Project

General

Profile

Actions

Bug #8337

closed

Broken compliance summary on a node

Added by Alexis Mousset almost 8 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

See attached screenshot, it seems there is an issue in the computation of global compliance for the node.


Files

compliance.png (34 KB) compliance.png Alexis Mousset, 2016-05-19 13:22

Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Bug #8051: Compliance is not correctly computed if we receive run agent right after generationReleasedNicolas CHARLES2016-05-19Actions
Actions #1

Updated by Alexis Mousset almost 8 years ago

I reloaded the page and another directive appeared as missing.

Actions #2

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.10 to 3.1.11
Actions #3

Updated by François ARMAND almost 8 years ago

  • Related to Bug #8051: Compliance is not correctly computed if we receive run agent right after generation added
Actions #4

Updated by François ARMAND almost 8 years ago

We believe it could have been to #8051.

We are closing that one, but we are keeping an eye open to that problem in the future.

Actions #5

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions #6

Updated by François ARMAND almost 8 years ago

  • Status changed from New to Rejected
Actions #7

Updated by François ARMAND almost 8 years ago

  • Related to deleted (Bug #8051: Compliance is not correctly computed if we receive run agent right after generation)
Actions #8

Updated by François ARMAND almost 8 years ago

  • Is duplicate of Bug #8051: Compliance is not correctly computed if we receive run agent right after generation added
Actions

Also available in: Atom PDF