Actions
Feature #24923
closedAdd check for puppet class duplicates
Difficulty:
Triaged:
No
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.
Updated by Ondřej Pražák over 6 years ago
- Related to Bug #24633: Duplicate puppet classes are created when publishing content views in parallel added
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_maintain/pull/212 added
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/theforeman/foreman_maintain/pull/215 added
Updated by Ivan Necas over 6 years ago
- Status changed from Ready For Testing to Closed
Updated by Ivan Necas about 6 years ago
- Fixed in Releases foreman_maintain-0.3.0 added
Actions