Bug 1386192

Summary: Rerun on host selects in job invocation again all hosts instead of supplied hosts_ids from url
Product: Red Hat Satellite Reporter: Peter Vreman <peter.vreman>
Component: Remote ExecutionAssignee: Ivan Necas <inecas>
Status: CLOSED ERRATA QA Contact: Adam Ruzicka <aruzicka>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.2CC: aruzicka, asahni, bbuckingham, brubisch, carlospec, dmoessne, doug.crozier, inecas, jcallaha, peter.vreman, sjr, vgunasek
Target Milestone: UnspecifiedKeywords: Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:59:17 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:
Bug Depends On:    
Bug Blocks: 1122832    
Attachments:
Description Flags
select rerun on a single host
none
hosts_ids in url is not used, query is still used instead none

Description Peter Vreman 2016-10-18 11:39:39 UTC
Description of problem:
The option to 'rerun' on hosts shall rerun the current jobtemplate again on the host without going to create a full new invocation of the complete job.

There are 2 issues with this:
- It selects again all hosts, even that the URL has hosts_id=[X] in it
- It allows editing of the template etc.


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


How reproducible:


Steps to Reproduce:
1. Execute a job on 5 hosts
2. Goto Hosts tab
3. Select rerun on 1 hosts

Actual results:
New job invocation is started with the full query and allow to edit

Expected results:
The same job is executed at the host again without going through the whole process again.


Additional info:

Comment 3 Ivan Necas 2017-04-18 15:32:38 UTC
I don't think we change the behavior as there is an value in the original workflow as well. Would providing an option behind a dropdown to 'Rerun immediately' be sufficient enough for this request?

Comment 4 Peter Vreman 2017-04-19 08:57:18 UTC
Hoi Ivan.

Sorry, the current behavior is a bug. It does reflect what is written on the action button and what then passed on the URL.
See the attached screenshots where i select rerun on a host.
Then in the next screen i see in the URL the host_ids, but in the query below this value is not used.

As a user i expect that the host_ids is used and overrides (disables) the query field to execute it only on those hosts selected by host_ids.

Comment 5 Peter Vreman 2017-04-19 08:58:03 UTC
Created attachment 1272525 [details]
select rerun on a single host

Comment 6 Peter Vreman 2017-04-19 08:58:44 UTC
Created attachment 1272526 [details]
hosts_ids in url is not used, query is still used instead

Comment 7 Ivan Necas 2017-04-19 14:08:47 UTC
Created redmine issue http://projects.theforeman.org/issues/19320 from this bug

Comment 8 Ivan Necas 2017-04-19 14:11:39 UTC
Thanks for the screenshots, I understand the issue now: the fix is sent upstream.

Comment 9 Satellite Program 2017-04-19 16:18:12 UTC
Upstream bug assigned to inecas

Comment 10 Satellite Program 2017-04-19 16:18:16 UTC
Upstream bug assigned to inecas

Comment 11 Satellite Program 2017-04-20 10:18:38 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19320 has been resolved.

Comment 12 Adam Ruzicka 2017-06-13 07:53:44 UTC
*** Bug 1460780 has been marked as a duplicate of this bug. ***

Comment 15 Adam Ruzicka 2017-08-02 12:56:55 UTC
Verified.
Satellite-6.3 Snap 9
Package versions:
satellite-6.3.0-16.0.beta.el7sat.noarch
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_15.el7sat.noarch

1) Run a job on 100 hosts
2) Wait for it to finish
3) Go to Hosts
4) Select rerun on one of the hosts
5) New job invocation's search query is set to target only the one host

Comment 16 Adam Ruzicka 2017-09-26 07:22:32 UTC
*** Bug 1495373 has been marked as a duplicate of this bug. ***

Comment 17 Bryan Kearney 2018-02-21 16:59:17 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