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 1254490 - Install Applicable Errata subtask doesn't show the hostname of the system it is applying the errata on.
Summary: Install Applicable Errata subtask doesn't show the hostname of the system it ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: Katello QA List
URL:
Whiteboard:
: 1326515 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-18 09:01 UTC by Fred van Zwieten
Modified: 2019-11-14 06:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-12 01:11:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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. ***
Note You need to log in before you can comment on or make changes to this bug.