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 1973652 - Tasks page shows "Could Not Receive Data: Request Failed With Status Code 500" error after upgrading satellite to 6.9.3 snap 3
Summary: Tasks page shows "Could Not Receive Data: Request Failed With Status Code 500...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.9.3
Assignee: Adam Ruzicka
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-18 12:07 UTC by Jameer Pathan
Modified: 2021-07-01 14:57 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman-tasks-3.0.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-01 14:56:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32838 0 Normal New Tasks page shows "Could Not Receive Data: Request Failed With Status Code 500" error after upgrading satellite to 6.9.3 ... 2021-06-18 14:59:22 UTC
Red Hat Product Errata RHBA-2021:2636 0 None None None 2021-07-01 14:57:12 UTC

Description Jameer Pathan 2021-06-18 12:07:00 UTC
Description of problem:
Tasks page shows "Could Not Receive Data: Request Failed With Status Code 500" error after upgrading satellite to 6.9.3 snap 3

Version-Release number of selected component (if applicable):
- Satellite 6.9.3 snap 3

How reproducible:
- Always

Steps to Reproduce:
1. Install satellite 6.9.2
2. Import manifest
3. Register few host with satellite and insight.
4. sync RH cloud inventory and insights recommendations.
5. Upgrade Satellite to 6.9.3 snap 3
6. Go to Monitor Tasks page

Actual results:
Tasks page shows "Could Not Receive Data: Request Failed With Status Code 500" error.

Expected results:
- No error

Additional info:

Comment 3 Adam Ruzicka 2021-06-18 14:59:19 UTC
Created redmine issue https://projects.theforeman.org/issues/32838 from this bug

Comment 5 Adam Ruzicka 2021-06-21 14:29:57 UTC
Fix was released in upstream in foreman-tasks-3.0.6.

Comment 6 Jameer Pathan 2021-06-22 09:52:23 UTC
Verified:

Verified with: 
- Satellite 6.9.3 snap 4
- tfm-rubygem-foreman-tasks-3.0.6-1.el7sat.noarch

Test steps:
1. Install satellite 6.9.2
2. Import manifest
3. Register few host with satellite and insight.
4. sync RH cloud inventory and insights recommendations.
5. Upgrade Satellite to 6.9.3 snap 3
6. Go to Monitor Tasks page

Observation:
- No error on tasks page.

Comment 11 errata-xmlrpc 2021-07-01 14:56:50 UTC
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 (Satellite 6.9.3 Async Bug Fix Update), 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/RHBA-2021:2636


Note You need to log in before you can comment on or make changes to this bug.