Bug #30843
seeding fails with 'This template is locked. Please clone it to a new template to customize.'
Difficulty:
Triaged:
No
Description
https://github.com/theforeman/foreman/commit/f70392468ab8e23e5d0d5b2aef2a442408d7e47b added support for enforcing the lock for template inputs, however it did not take into account seeding the same way that template locking does
related to #28210
Related issues
Associated revisions
History
#1
Updated by Justin Sherrill over 2 years ago
Updated by - Related to Bug #28210: Can edit template inputs of locked template through CLI and API added
#2
Updated by The Foreman Bot over 2 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7992 added
#3
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/theforeman/foreman/pull/7996 added
#4
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/theforeman/foreman/pull/7998 added
#5
Updated by Ondřej Ezr over 2 years ago
Updated by - Pull request deleted (
https://github.com/theforeman/foreman/pull/7996)
#6
Updated by The Foreman Bot over 2 years ago
- Fixed in Releases 2.3.0 added
#7
Updated by Justin Sherrill over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|c84288327d49a3b16f802a0917d84c3a67a77ec3.
#8
Updated by Justin Sherrill about 1 year ago
- Related to Bug #34299: Upgrade fails during db:seed with ActiveRecord::RecordNotDestroyed: Failed to destroy the record added
Fixes #30843 - check for seeding on template input lock