Bug #26774
closed
Clean up reporting node compliance tables
Added by François ARMAND 2 months ago.
Updated about 2 months ago.
Category:
Architecture - Code maintenance
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.
- Related to Bug #26773: Do not store nodecompliancelevels by default added
- Description updated (diff)
- 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.
- Status changed from New to In progress
- Assignee set to François ARMAND
- Subject changed from Clean up nodecompliancetables to Clean up reporting node compliance tables
- Description updated (diff)
- 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
- Status changed from Pending technical review to Pending release
- 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
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.3.1 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by Anonymous 
Updated by 
Updated by