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:

In the web UI, trying to use remote execution to install a package to a content host fails

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

How reproducible:
I ran test multiple times

Steps to Reproduce:
1. Configure a RHEL8 content host
2. enable a module stream:
On the CHosts module streams tab, search for a stream
e.g:
 name = duck stream = 0

Note the status

3. From the actions menu, select some other status

Actual results:
An error page is displayed:
ERF42-5962 [Foreman::Exception]: No template mapped to feature Katello: Module Stream Actions

Expected results:
A REX job should run to complete this task

Additional info:
Has happened before but not in a GA version
https://bugzilla.redhat.com/show_bug.cgi?id=1886481

Does it go away if you rerun the seeds with foreman-rake db:seed?

(In reply to Adam Ruzicka from comment #3)
> Does it go away if you rerun the seeds with foreman-rake db:seed?

In some cases; I ran that on command a Sat6.9.2 and it worked, but not on my 6.10.0-3.0

Thank you

Created redmine issue https://projects.theforeman.org/issues/33024 from this bug

*** Bug 1990998 has been marked as a duplicate of this bug. ***

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