Bug #8032: Incomplete reporting in service management - Rudder - Issue Tracker

Actions

Bug #8032

closed

Incomplete reporting in service management

Added by Nicolas CHARLES over 9 years ago. Updated over 9 years ago.

Status:

Released

Priority:

N/A

Assignee:

Category:

Techniques

Target version:

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

Actions

#1

Updated by Nicolas CHARLES over 9 years ago

Status changed from New to In progress

Actions

#2

Updated by Nicolas CHARLES over 9 years ago

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

PR https://github.com/Normation/rudder-techniques/pull/891

Actions

#3

Updated by Nicolas CHARLES over 9 years ago

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

Actions

#4

Updated by Nicolas CHARLES over 9 years ago

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

Applied in changeset rudder-techniques|6f7b5f369cc308fa502611565a012403fcd8f43c.

Actions

#5

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 2.11.20 to 2.11.19

Actions

#6

Updated by Vincent MEMBRÉ over 9 years ago

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.

2.11: Announce Changelog
3.0: Announce Changelog
3.1: Announce Changelog
3.2: Announce Changelog
Download: https://www.rudder-project.org/site/get-rudder/downloads/

Actions

Also available in: Atom PDF