Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1516623

Summary: [RFE] The job invocations page should show the total number of hosts on which the job has to run
Product: Red Hat Satellite Reporter: sbadhwar
Component: Remote ExecutionAssignee: Dmitri Dolguikh <ddolguik>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: aruzicka, bkearney, inecas, jhutar, mhulan, psuriset, sbadhwar, sgraessl, tbrisker
Target Milestone: 6.4.0Keywords: FutureFeature, PrioBumpPM, RFE, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: scale_lab
Fixed In Version: tfm-rubygem-foreman_remote_execution-1.5.2-2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 15:29:23 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:
Attachments:
Description Flags
Job invocations page when 30k hosts were running Remote execution none

Description sbadhwar 2017-11-23 06:37:06 UTC
Created attachment 1358012 [details]
Job invocations page when 30k hosts were running Remote execution

Description of problem:
So, during the scale testing, we ran Remote Execution on 30k hosts. Now when we open the job invocations page it shows only the amount of hosts queued for execution and not all the hosts on which the task has to run (as shown in the attachment).

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


How reproducible:
Everytime


Steps to Reproduce:
1. Run a Remote Execution on large number of hosts
2. Open the job invocation page

Actual results:
Job Invocation page shows the number of queued tasks on which the tasks should be executed


Expected results:
Job Invocations page should show the total number of hosts on which the job should be executed

Comment 2 Adam Ruzicka 2017-11-30 09:13:33 UTC
Created redmine issue http://projects.theforeman.org/issues/21810 from this bug

Comment 3 Satellite Program 2018-04-17 20:20:03 UTC
Upstream bug assigned to ddolguik

Comment 4 Satellite Program 2018-04-17 20:20:08 UTC
Upstream bug assigned to ddolguik

Comment 5 Satellite Program 2018-04-27 12:19:49 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21810 has been resolved.

Comment 8 Peter Ondrejka 2018-09-13 13:16:26 UTC
Verified on satellite 6.4 snap 21, total hosts count is now correctly displayed

Comment 10 errata-xmlrpc 2018-10-16 15:29:23 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-2018:2927