Bug 1254490

Summary:	Install Applicable Errata subtask doesn't show the hostname of the system it is applying the errata on.
Product:	Red Hat Satellite	Reporter:	Fred van Zwieten <fvzwieten>
Component:	Errata Management	Assignee:	Ivan Necas <inecas>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	bbuckingham, cdonnell, cwelton, pghadge, smeyer
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-12 01:11:37 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 Fred van Zwieten 2015-08-18 09:01:58 UTC

Description of problem:
We had a situation that one of the subtasks of applying applicable errata failed because the host timed out. This will be a very common scenario. However, never in the subtask details the affected host is named.

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


How reproducible:
Choose one host and disable goferd. Create a job to apply to multiple hosts. Notice that one subtask will fail. Look at the subtask details and try to find the affected hostname.

Steps to Reproduce:
1.
2.
3.

Actual results:
No hostname to be found

Expected results:
the hostname is in the details

Additional info:

Comment 1 Brad Buckingham 2015-10-23 15:23:35 UTC

Ideally, we'd like to have a generic solution that can provide details on the object name that is being operated on or the external system being interfaced with (e.g. capsule name).

Comment 6 Ivan Necas 2017-05-10 13:31:58 UTC

*** Bug 1326515 has been marked as a duplicate of this bug. ***