Project

General

Profile

Actions
Copy link

Bug #10035

open

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

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

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

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

Actions
Copy link
 #1

Updated by Marek Hulán about 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.

Actions
Copy link
 #2

Updated by Jérôme Vizcaino about 10 years ago

Smart vars are not deleted when puppet classes are removed.

Actions
Copy link

Also available in: Atom PDF