Project

General

Profile

Actions
Copy link

Bug #15372

closed

Missing logs on NodeCompliance archive/deletion

Added by Nicolas CHARLES over 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
5.0.13
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

We don't have logs on success of NodeCompliance deletion/archive, simply a complete log - it's not really useful, as we may not have the error showing up.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #14003: nodecompliancelevels is not purgedRejectedActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions
Copy link
 #2

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/2357
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 5 years ago

  • Related to Bug #14003: nodecompliancelevels is not purged added
Actions
Copy link
 #4

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #5

Updated by François ARMAND about 5 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.13 which was released today.

Actions
Copy link

Also available in: Atom PDF