Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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.

Verified on satellite 6.10 sn 12

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