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 1771419

Summary:	'Rerun failed' sets execution order to alphabetical by default
Product:	Red Hat Satellite	Reporter:	Peter Dragun <pdragun>
Component:	Remote Execution	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Peter Dragun <pdragun>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	aruzicka, egolov, inecas
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_remote_execution-2.0.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:26:24 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:

Description Peter Dragun 2019-11-12 10:37:16 UTC

Description of problem:
When I try to rerun failed jobs, ordering is always set to alphabetical even if original job was executed with randomized order.


Version-Release number of selected component (if applicable):
Sat 6.7 snap 1

How reproducible:
always

Steps to Reproduce:
1. Run job with randomized ordering
2. Some subtask has failed
3. Click on 'Rerun failed'
4. In advanced fields check 'Execution ordering' 

Actual results:
'Execution ordering' is set to 'Alphabetical'

Expected results:
'Execution ordering' is set to 'Randomized'

Additional info:
'Rerun' works as expected

Comment 3 Adam Ruzicka 2019-11-12 11:28:44 UTC

Created redmine issue https://projects.theforeman.org/issues/28242 from this bug

Comment 4 Bryan Kearney 2019-11-12 13:00:25 UTC

Upstream bug assigned to aruzicka

Comment 5 Bryan Kearney 2019-11-12 13:00:28 UTC

Upstream bug assigned to aruzicka

Comment 6 Bryan Kearney 2019-11-20 15:00:33 UTC

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

Comment 7 Peter Dragun 2019-11-25 12:07:18 UTC

Verified on sat 6.7 snap 3.
On 'Rerun failed' execution order is set as on original job.

Comment 10 errata-xmlrpc 2020-04-14 13:26:24 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-2020:1454