Bug 1983043

Summary:	undefined method `prune_known_hosts!` when executing a remote job
Product:	Red Hat Satellite	Reporter:	Peter Ondrejka <pondrejk>
Component:	Remote Execution	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	aruzicka, lstejska, pcreech, swadeley
Target Milestone:	6.10.0	Keywords:	TestBlocker, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_remote_execution_core-1.4.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:12:34 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 Ondrejka 2021-07-16 10:18:37 UTC

Description of problem:

Executing a rex command on a host registered to a capsule fails with:

Error initializing command: NoMethodError - undefined method `prune_known_hosts!' for ForemanRemoteExecutionCore::Utils:Module
Did you mean?  prune_known_hosts
Exit status: EXCEPTION

Version-Release number of selected component (if applicable):
Satellite 6.10 snap 9

How reproducible:
always

Steps to Reproduce:
1. register a host to a non-internal capsule
2. run rex command

Actual results:
above exception

Expected results:
successful run

Additional info:
- host registered to the internal capsule didn't show this error
- the external capsule and host are both fips-enabled, not sure it bears significance here

Comment 1 Adam Ruzicka 2021-07-16 10:42:16 UTC

Workaround:
Just run the job again. Until the fix gets in, it will fail for the first time a job is executed on a host through a given capsule. Following executions through the same capsule should then work.

> the external capsule and host are both fips-enabled, not sure it bears significance here

It should not.

> 1. register a host to a non-internal capsule
> host registered to the internal capsule didn't show this error

Where a host is registered should not matter.

Comment 2 Peter Ondrejka 2021-08-06 13:24:12 UTC

Verified on satellite 6.10 sn 12

Comment 5 errata-xmlrpc 2021-11-16 14:12:34 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 (Moderate: Satellite 6.10 Release), 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-2021:4702