Actions
Bug #10035
open
Deletion of puppet classes doesn't remove associated references in other tables
Status:
New
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Description
Problem: When the puppet modules were deleted, the config_groups_classes table was not removed so when the puppet modules were re-imported, config_groups still showed a count of puppet modules even though there were none assigned. All the IDs were the old IDs of the puppet modules.
According to the IRC chat room:
<mhulan> BeeAyeEye: the bug is that we don't remove associations and we miss foreign keys there, could you report that please?
Currently running 1.7.4
Updated by Marek Hulán almost 10 years ago
- Category set to Database
- Translation missing: en.field_release deleted (
40)
Thanks for the report, just one clarification, only associations between config groups and puppet classes remained in DB, others seems to be removed properly.
Updated by Jérôme Vizcaino almost 10 years ago
Smart vars are not deleted when puppet classes are removed.
Actions