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.
Created attachment 989589[details]
On selecting any fact with integer value from auto-search under New discovery rule form, raises 500 ISE
Description of problem:
While defining the discovery rule, in search box I choose the auto-search and defined "cpu_count = 1"
As soon as I defined "cpu_count = 1" in serach, UI raises 500 ISE in firebug and poduction.log thrown:
--
Processing by DiscoveredHostsController#auto_complete_search as JSON
Parameters: {"search"=>" cpu_count = 1"}
Operation FAILED: PGError: ERROR: operator does not exist: integer ~~ unknown
LINE 1: ...s" WHERE ("discovery_attribute_sets"."cpu_count" LIKE '1%')...
^
HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts.
: SELECT DISTINCT "discovery_attribute_sets"."cpu_count" FROM "discovery_attribute_sets" WHERE ("discovery_attribute_sets"."cpu_count" LIKE '1%') ORDER BY "discovery_attribute_sets"."cpu_count" LIMIT 20
Rendered common/500.html.erb (5.2ms)
Completed 500 Internal Server Error in 22ms (Views: 6.0ms | ActiveRecord: 2.0ms)
--
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150205.0
Sat6.1 Beta snap1 compose3
How reproducible:
always
Steps to Reproduce:
1. go to configure --> New discovery rule
2. from auto-serach choose any fact like cpu_count = 1
3. see production.log
Actual results:
firebug raises following:
"NetworkError: 500 Internal Server Error - https://dhcp201-137.englab.pnq.redhat.com/discovered_hosts/auto_complete_search?search=+cpu_count+%3D+1
production.log raises:
-
--
Processing by DiscoveredHostsController#auto_complete_search as JSON
Parameters: {"search"=>" cpu_count = 1"}
Operation FAILED: PGError: ERROR: operator does not exist: integer ~~ unknown
LINE 1: ...s" WHERE ("discovery_attribute_sets"."cpu_count" LIKE '1%')...
^
HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts.
: SELECT DISTINCT "discovery_attribute_sets"."cpu_count" FROM "discovery_attribute_sets" WHERE ("discovery_attribute_sets"."cpu_count" LIKE '1%') ORDER BY "discovery_attribute_sets"."cpu_count" LIMIT 20
Rendered common/500.html.erb (5.2ms)
Completed 500 Internal Server Error in 22ms (Views: 6.0ms | ActiveRecord: 2.0ms)
--
On selecting any fact with integer value from auto-search under New discovery rule form.
Expected results:
No error should appear in production.log and Firebug shouln't raise any error on selecting fact from auto-search with integer value
Additional info:
When you see 500 in the UI that's totally blocker, but in this case we only see 500 only in the production.log. Satellite 6 operates well. For this reason I gave it lower prio.