Project

General

Profile

Actions
Copy link

Bug #8032

closed

Incomplete reporting in service management

Bug #8032: Incomplete reporting in service management

Added by Nicolas CHARLES almost 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Techniques
Target version:
2.11.19
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When we manage twice the same service, we only get one report, so the compliance in invalid

Updated by Nicolas CHARLES almost 10 years ago Actions
Copy link
 #1

  • Status changed from New to In progress

Updated by Nicolas CHARLES almost 10 years ago Actions
Copy link
 #2

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/891

Updated by Nicolas CHARLES almost 10 years ago Actions
Copy link
 #3

  • Subject changed from Incomplete reporting in service management when managing twice the same service to Incomplete reporting in service management

The problem is more complex, the reporting in incomplete in many cases

Updated by Nicolas CHARLES almost 10 years ago Actions
Copy link
 #4

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

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

  • Target version changed from 2.11.20 to 2.11.19

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

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.

Actions
Copy link

Also available in: PDF Atom