Bug 1696625

Summary:	WebUI export task to contain task UUID
Product:	Red Hat Satellite	Reporter:	Pavel Moravec <pmoravec>
Component:	Tasks Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Peter Dragun <pdragun>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.5.0	CC:	aruzicka, inecas, pcreech, pdragun
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:24:10 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 Pavel Moravec 2019-04-05 09:51:56 UTC

Description of problem:
WebUI task export (not the one in foreman-debug) should contain UUID of the task. That is valuable for unique identification of the task, which further allows possible manipulation of given task (i.e. querying task details via API, cancelling just given task, or so).


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


How reproducible:
100%


Steps to Reproduce:
1. WebUI: Monitor -> Tasks -> (optionally apply some filter) -> Export


Actual results:
Export has columns:
Action	State	Result	Started At	Ended At	User


Expected results:
Export to have columns:
UUID    Action	State	Result	Started At	Ended At	User


Additional info:

Comment 3 Bryan Kearney 2019-06-17 14:07:42 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26544 has been resolved.

Comment 4 Peter Dragun 2019-12-02 12:08:04 UTC

Verified on Satellite 6.7 snap 4
Export now has 'Id' column with task UUID.

Id,Action,State,Result,Started At,Ended At,User
01c4b03f-3d79-401a-9a3a-d17775f0854e,Subscription expiration notification,stopped,success,2019-11-29 22:13:41 UTC,2019-11-29 22:13:42 UTC,

Comment 7 errata-xmlrpc 2020-04-14 13:24:10 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, 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-2020:1454