Project

General

Profile

Bug #10035

Deletion of puppet classes doesn't remove associated references in other tables

Added by Brian Imbriani about 7 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

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

History

#1 Updated by Marek Hulán about 7 years ago

  • Category set to Database
  • Legacy Backlogs Release (now unused) 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.

#2 Updated by Jérôme Vizcaino about 7 years ago

Smart vars are not deleted when puppet classes are removed.

Also available in: Atom PDF