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.
Bug 1440157 - Long integer value in Tasks on Satellite WebU gives error: Oops, we're sorry but something went wrong PG::Error: ERROR: value "1489607391328" is out of range for type integer
Summary: Long integer value in Tasks on Satellite WebU gives error: Oops, we're sorry...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.2.8
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-07 12:22 UTC by Renu Chauhan
Modified: 2021-12-10 14:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 14:49:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19246 0 None None None 2017-04-11 12:35:48 UTC

Description Renu Chauhan 2017-04-07 12:22:22 UTC 
Description of problem:

When put a long integer, 1489607391328 for example into the Task Search then receive the following error:

Oops, we're sorry but something went wrong PG::Error: ERROR: value "1489607391328" is out of range for type integer LINE 11: WHERE "foreman_tasks_task_groups"."id" = '1489607391328' ))... ^ : SELECT DISTINCT "foreman_tasks_tasks"."id", "foreman_tasks_tasks"."started_at" AS alias_0 FROM "foreman_tasks_tasks" INNER JOIN "foreman_tasks_locks" ON "foreman_tasks_locks"."task_id" = "foreman_tasks_tasks"."id" LEFT OUTER JOIN "foreman_tasks_task_group_members" ON "foreman_tasks_task_group_members"."task_id" = "foreman_tasks_tasks"."id" LEFT OUTER JOIN "foreman_tasks_task_groups" ON "foreman_tasks_task_groups"."id" = "foreman_tasks_task_group_members"."task_group_id" INNER JOIN foreman_tasks_locks AS foreman_tasks_locks_owner ON (foreman_tasks_locks_owner.task_id = foreman_tasks_tasks.id AND foreman_tasks_locks_owner.resource_type = 'User' AND foreman_tasks_locks_owner.name = 'task_owner') INNER JOIN users ON (users.id = foreman_tasks_locks_owner.resource_id) WHERE (("foreman_tasks_tasks"."id" ILIKE '%1489607391328%' OR "foreman_tasks_tasks"."label" ILIKE '%1489607391328%' OR "foreman_tasks_tasks"."state" ILIKE '%1489607391328%' OR "foreman_tasks_tasks"."result" ILIKE '%1489607391328%' OR "foreman_tasks_tasks"."parent_task_id" ILIKE '%1489607391328%' OR foreman_tasks_locks."resource_type" ILIKE '1489607391328' OR foreman_tasks_locks."resource_type" = '1489607391328' OR users.login = '1489607391328' or users.firstname = '1489607391328' OR users.login ILIKE '1489607391328' or users.firstname ILIKE '1489607391328' OR users.login ILIKE '1489607391328' or users.firstname ILIKE '1489607391328' OR "foreman_tasks_tasks"."id" IN (SELECT "foreman_tasks_tasks"."id" FROM "foreman_tasks_tasks" INNER JOIN "foreman_tasks_task_group_members" ON "foreman_tasks_tasks"."id" = "foreman_tasks_task_group_members"."task_id" INNER JOIN "foreman_tasks_task_groups" ON "foreman_tasks_task_group_members"."task_group_id" = "foreman_tasks_task_groups"."id" WHERE "foreman_tasks_task_groups"."id" = '1489607391328' ))) ORDER BY "foreman_tasks_tasks"."started_at" DESC NULLS LAST LIMIT 20 OFFSET 0

and in the tasks state it gives error as: 

Runtime Error RESTEASY001185: Could not find resource for relative : /products//content/1489607391328 of full path: https://localhost:8443/candlepin/products//content/1489607391328?enabled=true at org.jboss.resteasy.core.registry.PathParamSegment.matchPattern:209"



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Go to Satellite WebUI --> Monitor --> Tasks --> Put the integer value (Eg 1489607391328
2.
3.

Actual results:
A error message is displayed

Expected results:
It should show the task.

Additional info:
Comment 3 Adam Ruzicka 2017-04-11 12:35:44 UTC 
Created redmine issue http://projects.theforeman.org/issues/19246 from this bug
Comment 4 Bryan Kearney 2018-11-01 14:43:28 UTC 
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is  not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Rich Jerrido or Bryan Kearney or your account team. If we do not hear from you, we will close this bug out. Thank you.
Comment 5 Bryan Kearney 2018-11-30 14:49:16 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Note You need to log in before you can comment on or make changes to this bug.