Bug 1460780

Summary: Re-Run failed remote execution task for single content host takes 'Host Collection' instead of single content host.
Product: Red Hat Satellite Reporter: Varatharaja Perumal G <vgunasek>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.9CC: aruzicka, carlospec, inecas
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-13 07:53:44 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 Varatharaja Perumal G 2017-06-12 17:26:51 UTC 
Description of problem:

When we run a remote execution job for multiple content host through 'Host Collection'. When we re-run the remote execution for single content host it takes 'Host Collection' instead of single content host.

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

How reproducible:


Steps to Reproduce:
1. Create a 'Host Collection' with multiple content host.
2. Run the remote execution task for the 'Host Collection'
3. On the remote execution result screen. Select Hosts tab.
4. Hosts --> Select (host) --> Action -->  drop down -> Rerun (host)
5. It will take the 'Host Collection' instead of selected host.

Actual results:

It take 'Host Collection' instead of single host to run the job.

Expected results:

It should run for single host instead of 'Host Collection'

Additional info:
Comment 2 Varatharaja Perumal G 2017-06-12 17:30:42 UTC 
Created attachment 1287080 [details]
Host collection
Comment 3 Varatharaja Perumal G 2017-06-12 17:32:12 UTC 
Created attachment 1287081 [details]
Host collection
Comment 5 Adam Ruzicka 2017-06-13 07:53:44 UTC 
Even though this BZ isn't an exact duplicate of the linked one, they share the same root cause.

*** This bug has been marked as a duplicate of bug 1386192 ***