Project

General

Profile

Actions

Feature #24923

closed

Add check for puppet class duplicates

Added by Ondřej Pražák over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Fixed in Releases:
Found in Releases:

Description

When concurrently publishing content views with the same name, duplicate records for Puppet class may be created in Foreman db because Rails validation gets bypassed and there is no uniqueness constraint on db. If there are existing deployments with duplicates, it is not feasible to delete/rename them automatically, because there may be custom overrides configured for the classes. We should ask users to remove the duplicates before proceeding.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #24633: Duplicate puppet classes are created when publishing content views in parallelClosedOndřej PražákActions
Actions #1

Updated by Ondřej Pražák over 5 years ago

  • Related to Bug #24633: Duplicate puppet classes are created when publishing content views in parallel added
Actions #2

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_maintain/pull/212 added
Actions #3

Updated by The Foreman Bot over 5 years ago

  • Pull request https://github.com/theforeman/foreman_maintain/pull/215 added
Actions #4

Updated by Ivan Necas over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by Ivan Necas over 5 years ago

  • Fixed in Releases foreman_maintain-0.3.0 added
Actions

Also available in: Atom PDF