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.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6/html-single/managing_hosts/index#sect-Managing_Hosts-Executing_Remote_Jobs

Section Number and Name: 
8.4.2. Executing Jobs

Describe the issue: 
When running against a large number of servers, task execution runs are sorted by name. This can be awkward when servers with a similar name are in the same cluster.
Admins require an option to be able to randomize when running against multiple clusters of servers in one execution.


Suggestions for improvement:
Include information about this new feature in the Executing Jobs procedure. There are possibly Satellite web UI changes associated with the Job invocation page.

Upstream bug assigned to aruzicka

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24124 has been resolved.

Hi Bryan, 

Since this is a documentation bug, I don't think Adam will be too thrilled to be the assignee for this, thanks for volunteering him though :-)

Kind regards,
Vlada

Resetting Assignee to default, and status back to NEW, thanks!

Upstream bug assigned to aruzicka

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24124 has been resolved.