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.
Description of problem:
Satellite doesn't convert the matcher to downcase when adding a new matcher field and a matcher in one go from the Web UI.
Steps to Reproduce:
1) In the smart class parameter edit page you add a new "TesT" (title case) field to the Order textbox.
2) You have an existing matcher "fqdn=some.content.host.com".
2) Then click "Add Matcher" to add a new matcher "TesT=true".
3) Click the "submit" button to save
4) Revisit the "edit" page and get "Oops, we're sorry but something went wrong comparison of Array with Array failed"
Reason:
This is because Satellite converted the value in step (1) to down case but leaving the matcher in step (3) as it is. When rendering the page, Satellite can't find the field for the matcher in the list of array.
It found the index of "fqdn" in the array (return an integer) but can't find the index of "TesT" in the array (nil). Comparing nil with 1 raises the following error.
irb(main):002:0> [[nil], [1]].sort_by{|v| v}
ArgumentError: comparison of Array with Array failed
Actual results:
Can't access the edit page
Expected results:
Can access the edit page
Description of problem: Satellite doesn't convert the matcher to downcase when adding a new matcher field and a matcher in one go from the Web UI. Steps to Reproduce: 1) In the smart class parameter edit page you add a new "TesT" (title case) field to the Order textbox. 2) You have an existing matcher "fqdn=some.content.host.com". 2) Then click "Add Matcher" to add a new matcher "TesT=true". 3) Click the "submit" button to save 4) Revisit the "edit" page and get "Oops, we're sorry but something went wrong comparison of Array with Array failed" Reason: This is because Satellite converted the value in step (1) to down case but leaving the matcher in step (3) as it is. When rendering the page, Satellite can't find the field for the matcher in the list of array. It found the index of "fqdn" in the array (return an integer) but can't find the index of "TesT" in the array (nil). Comparing nil with 1 raises the following error. irb(main):002:0> [[nil], [1]].sort_by{|v| v} ArgumentError: comparison of Array with Array failed Actual results: Can't access the edit page Expected results: Can access the edit page