Bug 1524539

Summary:	[RFE] Remote execution jobs use hosts content source by default, if content source is set.
Product:	Red Hat Satellite	Reporter:	Paul Dudley <pdudley>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.12	CC:	aruzicka, bkearney, cmarinea, inecas, pdudley
Target Milestone:	Unspecified	Keywords:	FutureFeature
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-01-18 19:27: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:

Description Paul Dudley 2017-12-11 16:30:08 UTC

Description of problem:
Currently we can either set a subnet (and remote execution capsule through the subnet) or distribute all capsule ssh keys to all clients in case a subnet isn't defined for a host. In some environments with a lot of subnets this ends up being inconvenient. 

If the content source is set for a host (via host group) it would seem that the preferred capsule has already been chosen for the host. In these cases, it would be more convenient to distribute only the content source ssh key and define the remote execution capsule for the particular host as well.

Comment 1 Ivan Necas 2017-12-12 08:30:46 UTC

This should already be the case currently: we look at the all capsules assigned to the host with remote execution feature and use it as pool of capsules to be used.

If that is not the case, see https://bugzilla.redhat.com/show_bug.cgi?id=1508153#c3 for providing more info on the current setup.

Comment 2 Paul Dudley 2018-01-11 22:27:31 UTC

The issue here for this customer was that there is a large pool of capsules (12) and an even larger pool of subnets, where making a host group for each subnet would mean managing more than 40 or 50 subnets/hostgroups. In this case, the only reason for making so many would be to provide a 'specific' capsule for remote execution.

If we're already defining a content_source to be a specific capsule, we could define that same capsule as the remote execution capsule as well and offer another way to be specific for the remote execution capsule (and eliminate the need to distribute 12 ssh keys to all content hosts or manage a host group for each subnet).

Comment 3 Bryan Kearney 2018-01-18 19:27:32 UTC


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