Actions
Bug #17129
closed
When deletion of reports fails, we don't get meaningful message, and it fails when ComplianceLevels are disabled
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
the only log we have is:
Reports database: Error while processing database deleting, cause is: Failure(An error occured while processing: Empty,Empty,Empty)*
this isn't really helpful
Updated by Nicolas CHARLES about 4 years ago
- Subject changed from when deletion of reports fails, we don't get meaningful message to when deletion of reports fails, we don't get meaningful message, and it fails when ComplianceLevels are disabled
Updated by Nicolas CHARLES about 4 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 4 years ago
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2899
Updated by Nicolas CHARLES about 4 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder|9b1efd3db23040c983efb5a385acb2d7f85c2029.
Updated by Nicolas CHARLES about 4 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset almost 4 years ago
- Subject changed from when deletion of reports fails, we don't get meaningful message, and it fails when ComplianceLevels are disabled to When deletion of reports fails, we don't get meaningful message, and it fails when ComplianceLevels are disabled
Updated by Alexis Mousset almost 4 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ almost 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.17 and 6.0.5 which were released today.
Actions