Actions
Bug #26774
closed
Clean up reporting node compliance tables
Status:
Released
Priority:
N/A
Assignee:
Category:
Architecture - Code maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
See #26773 for why.
We have two table to clean-up:
- nodecompliance
- nodecompliancelevels
And their related options: rudder.save.db.compliance.details and rudder.save.db.compliance.levels
There is nothing to migrate, we just need to delete everything.
Updated by François ARMAND about 1 month ago
- Related to Bug #26773: Do not store nodecompliancelevels by default added
Updated by François ARMAND about 1 month ago
- Target version changed from 9.0.0~alpha1 to 8.3.1
Plugin is removed in 8.3, no need to keep that table more.
Updated by François ARMAND about 1 month ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 1 month ago
- Subject changed from Clean up nodecompliancetables to Clean up reporting node compliance tables
- Description updated (diff)
Updated by François ARMAND about 1 month ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/6339
Updated by Anonymous about 1 month ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|4cf701bccffbb7d203c8e2ec26b02e420802f9ab.
Updated by Clark ANDRIANASOLO about 1 month ago
- Fix check changed from To do to Checked
>>> psql -h localhost -U rudder rudder -c "\d nodecompliance " Did not find any relation named "nodecompliance".
, same for
nodelevels.
Also, the settings are removed, and all compliance seems to be working fine
Updated by Vincent MEMBRÉ 25 days ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.3.1 which was released today.
Actions