Created attachment 1508542 [details] Screenshot with issue Description of problem: Input any data to search field on Activation Key page and click 'Search' button. That action lead to SQL error and blocking of further search procedure Version-Release number of selected component (if applicable): 6.5.0 (latest snap on Nov 25) How reproducible: Always Steps to Reproduce: 1. Write any data to search field 2. Push 'Search' button 3. Actual results: Search functionality for activation keys doesn't work Expected results: You can use search functionality for activation keys Additional info:
Blocking each and every test automation scenario for activation key functionality without any easy workaround At that moment: ~26 of integration/system tests
*** Bug 1653325 has been marked as a duplicate of this bug. ***
this is the actual error external method 'find_by_subscription_id' failed with error: PG::InvalidTextRepresentation: ERROR: invalid input syntax for integer: "keyname" LINE 1: ...ivation_keys"."pool_id" WHERE (katello_pools.id = 'keyname') ^ : SELECT "katello_activation_keys"."id" FROM "katello_activation_keys" INNER JOIN "katello_pool_activation_keys" ON "katello_pool_activation_keys"."activation_key_id" = "katello_activation_keys"."id" INNER JOIN "katello_pools" ON "katello_pools"."id" = "katello_pool_activation_keys"."pool_id" WHERE (katello_pools.id = 'keyname') changing component to Search
Created redmine issue https://projects.theforeman.org/issues/25599 from this bug
Verified on 6.5.0 snap 9 List of packages: candlepin-2.5.8-1.el7.noarch candlepin-selinux-2.5.8-1.el7.noarch foreman-1.20.1.2-1.el7sat.noarch foreman-bootloaders-redhat-201801241201-3.el7sat.noarch foreman-bootloaders-redhat-tftpboot-201801241201-3.el7sat.noarch foreman-cli-1.20.1.2-1.el7sat.noarch foreman-compute-1.20.1.2-1.el7sat.noarch foreman-debug-1.20.1.2-1.el7sat.noarch foreman-discovery-image-3.5.3-1.el7sat.noarch ... 1) Executed `test_positive_end_to_end_crud` from ui_airgun/test_activationkey.py 2) Manually using next search scenario a) `test_name1` b) `test_name2` c) `name = test_name1` d) `name ~ test_name` e) `environment = Library` All scenario works as expected
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222