Bug 1481981

Summary: Rerun failed form doesn't select the type of query
Product: Red Hat Satellite Reporter: Ivan Necas <inecas>
Component: Remote ExecutionAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: aruzicka, bbuckingham, bkearney, inecas, jcallaha
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_remote_execution 1.3.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 17:09:32 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
screenshot of missing set of type of execution none

Description Ivan Necas 2017-08-16 08:26:47 UTC 
Created attachment 1313993 [details]
screenshot of missing set of type of execution

Description of problem:


Version-Release number of selected component (if applicable):
Sat 6.3 snap 11

How reproducible:
Always

Steps to Reproduce:
1. run job on hosts that leads to failures
2. use 'Rerun failed' after the job finishes
3. hit "Submit"

Actual results:
The job invocation form is showed again, without any indication what's wrong.
The reason is the "Type of query" is unselected, see attachments

Expected results:
The type of query is set as 'Static'

Workaround
Set the 'Static' query manually.


Additional info:
Fond during verification of https://bugzilla.redhat.com/show_bug.cgi?id=1406489
Comment 4 Adam Ruzicka 2017-08-17 13:29:34 UTC 
Created redmine issue http://projects.theforeman.org/issues/20630 from this bug
Comment 5 Satellite Program 2017-08-17 14:13:47 UTC 
Upstream bug assigned to aruzicka
Comment 6 Satellite Program 2017-08-17 14:13:49 UTC 
Upstream bug assigned to aruzicka
Comment 7 Satellite Program 2017-08-18 14:13:45 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20630 has been resolved.
Comment 9 Peter Ondrejka 2017-10-16 11:48:43 UTC 
Verified on satellite-6.3.0-20.0.beta.el7sat.noarch using execution steps from the problem description
Comment 10 Bryan Kearney 2018-02-21 17:09:32 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:0336