Bug #14007
closed
Indexes on nodecompliancelevels table are not valid and table ArchivedReportsExecution is never used
Added by Nicolas CHARLES over 5 years ago.
Updated about 5 years ago.
Category:
Plugins integration
Description
Indexes on nodecompliancelevels are not valid: we have 3 time the same index
CREATE INDEX nodecompliancelevels_nodeId ON nodecompliancelevels (nodeId);
CREATE INDEX nodecompliancelevels_ruleId ON nodecompliancelevels (nodeId);
CREATE INDEX nodecompliancelevels_directiveId ON nodecompliancelevels (nodeId);
- Subject changed from indexes on nodecompliancelevels table are not valid to indexes on nodecompliancelevels table are not valid and table ArchivedReportsExecution is never used
- Assignee set to Nicolas CHARLES
- Status changed from New to In progress
- 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/2101
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.8 and 5.0.4 which were released today.
Changelog
Changelog
- Subject changed from indexes on nodecompliancelevels table are not valid and table ArchivedReportsExecution is never used to Indexes on nodecompliancelevels table are not valid and table ArchivedReportsExecution is never used
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by