Bug #12339
closedDeleting the existing matcher and creating the same again throws error 'Match has already been taken'.
Description
Description of problem:
In Configure -> smart class parameter, deleting the existing matcher and without saving the changes, creating the same again throws error 'Match has already been taken'.
Version-Release number of selected component (if applicable):
foreman-1.11.0-0.develop.201510221551git1d0315e.el7.noarch
How reproducible:
Always
Steps to Reproduce:
1. Create matcher for puppet class parameter with some attribute and some value.
2. Save the changes.
3. Again edit the puppet class parameter to delete the matcher created in step 1.
4. Without saving changes of step 3 in parameter, create the matcher with same attribute and same value as created in step 1 and try to save the change to the parameter.
Actual results:
The error of 'Match has already been taken' is displayed and not allowing to save the changes.
Expected results:
Deleting and creating of matcher with same attribute and value should be allowed without saving the changes to parameter.
Files
Updated by Dominic Cleal about 9 years ago
- Translation missing: en.field_release deleted (
71)
Please don't set the release field on tickets.
Updated by Adam Ruzicka over 8 years ago
- Status changed from New to Assigned
- Assignee set to Adam Ruzicka
Updated by The Foreman Bot over 8 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3507 added
Updated by Adam Ruzicka over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 88e4eb7c3efb86ebd870b924771bdfc5bf8d7b06.
Updated by Dominic Cleal over 8 years ago
- Translation missing: en.field_release set to 136