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:

Run patch update with Remote Execution on scale setup. 
There might be failures for 2 different reasons

   1) satellite issues
   2) hosts side issues

Cant filter the failure nodes in such large scale setup. 



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


How reproducible:


Steps to Reproduce:
1. Update patch on scale setup 
2. Filter failed ones.
3.

Actual results:


Expected results:


Additional info:

Workaround:

in the job invocation page, click to "Rerun failed". Search query will then conatin the names of failed systems :)

Is just somehow obtaining a list of failed (and/or success) hosts enough for you or do you want to further split them into groups by "failure type"?

(In reply to aruzicka from comment #3)
> Is just somehow obtaining a list of failed (and/or success) hosts enough for
> you or do you want to further split them into groups by "failure type"?

would be good to split them into groups by "failure type". When we are running at large scale, it would be challenging to go through all of them. 
if we have seperate list, its easier to debug respective hosts based on failure type.

Marking as duplicate of BZ1423682 because it delivers almost what was requested in this BZ. Feel free to reopen this one if you feel the fix provided by the other BZ is inadequate.

*** This bug has been marked as a duplicate of bug 1423682 ***