Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJitendra Yejare
2015-10-28 09:57:49 UTC
Created attachment 1087194[details]
Screenshot Attached.
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.
Additional info:
Created attachment 1087194 [details] Screenshot Attached. 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. Additional info: