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:
Clicking some pending task in Monitor -> Tasks gives: "Oops, we're sorry but something went wrong state data not available"
Version-Release number of selected component (if applicable):
satellite-6.2.5-1.0.el7sat.noarch
How reproducible:
all the time on my setup for certain pending tasks
Steps to Reproduce:
1. I do not know how I got into this situation and whether it is general issue,
or something caused by some inconsistency on my setup, but might be connected
with bug 1400624
Actual results:
See traceback in attachement
Expected results:
Should show details about task with possibility to cancel it
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
I'm rather marking this as a duplicate for 1438601, as I believe the fix there should address this issues.
*** This bug has been marked as a duplicate of bug 1438601 ***