Project

General

Profile

Actions

Bug #5241

closed

In compliance popup, report status displayed for each node is not correct

Added by Nicolas PERRON over 10 years ago. Updated about 9 years ago.

Status:
Released
Priority:
2
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

The Compliance does not display the right status in the detail. The attached file show a Rule in 50% but all the nodes seems to be in No report status.


Files

ComplianceReportsFail.png (152 KB) ComplianceReportsFail.png Nicolas PERRON, 2014-07-08 15:51
Actions #1

Updated by Nicolas PERRON over 10 years ago

  • Category set to Web - Compliance & node report
  • Assignee set to Vincent MEMBRÉ
  • Priority changed from N/A to 2
  • Target version set to 2.11.0~rc2
Actions #2

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.11.0~rc2 to 2.11.0
Actions #3

Updated by Vincent MEMBRÉ over 10 years ago

  • Pull Request set to https://github.com/Normation/rudder/pull/575
Actions #4

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions #5

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #7

Updated by Vincent MEMBRÉ over 10 years ago

  • Subject changed from Rudder 2.11 compliance reports display only worst status on a Rule for every nodes even with other nodes in Success status to In compliance popup, report status displayed for each node is the worst for all nodes instead of being the status of the node
Actions #8

Updated by Vincent MEMBRÉ over 10 years ago

  • Subject changed from In compliance popup, report status displayed for each node is the worst for all nodes instead of being the status of the node to In compliance popup, report status displayed for each node is not correct
Actions #9

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.0 (announcement , changelog), which was released today.

Actions #10

Updated by Benoît PECCATTE about 9 years ago

  • Pull Request changed from https://github.com/Normation/rudder/pull/575 to https://github.com/Normation/rudder/pull/576
Actions

Also available in: Atom PDF