Bug 1400688

Summary:	clicking some pending task gives: "Oops, we're sorry but something went wrong state data not available"
Product:	Red Hat Satellite	Reporter:	Jan Hutař <jhutar>
Component:	Tasks Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.5	CC:	bbuckingham, bkearney, inecas, jcallaha, psuriset
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-13 18:02:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Hutař 2016-12-01 20:27:25 UTC

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

Comment 6 Bryan Kearney 2017-09-13 18:02:20 UTC

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.

Comment 7 Ivan Necas 2017-09-14 08:47:01 UTC

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 ***