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.

Created attachment 1759481 [details]
negative results displayed

Description of problem:

Satellite UI displays hosts as negative canceled for failed jobs 

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

Sat 6.8

How reproducible:

Customer Environment, for 500+ hosts, the graphical user interface is displaying wrong/misleading results

Steps to Reproduce:
1. Any ansible Job running a single Ansible role on 924 Hosts


Actual results:

After the job finished we got the result: 860 succeeded, 78 failed and *-14* were canceled (note that we did not cancel any task for this job). Also, note that the diagram shows -1.5% as canceled.
This seems to happen with several tasks if more than a few hosts are used.



Expected results:

Job-status for the hosts should not be in a negative state.

Since there was no response for a couple of months, I'll go ahead and close this as a duplicate of BZ #1531536. Feel free to reopen

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