Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Page breaks with "No template mapped to feature Run Puppet Once" error while trying to run puppet on host from Satellite.
Version-Release number of selected component (if applicable):
- Satellite 6.10.0 snap 6
How reproducible:
- Always
Steps to Reproduce:
1. Have a content host registered with Satellite
2. Go to hosts > All hosts, click on hostname.
3. Click on "Run Puppet once"
Actual results:
- "Oops, we're sorry but something went wrong ERF42-5962 [Foreman::Exception]: No template mapped to feature Run Puppet Once"
Expected results:
- Puppet run is successful
Additional info:
Looking at the reproducer, the template is present but going to administer -> remote execution features, it is not associated with the puppet_run_host feature.
Adam, any idea what could cause this? I did not find any changes touching the template or the association seed, and manually running the association from the seed in the console seems to work
I don't recall anything being touched recently. Apparently someone run into this in upstream with foreman 2.1[1], but it somehow resolved itself. I'll try poking around, but there's nothing that would immediately jump to mind.
[1] - https://projects.theforeman.org/issues/29950
Verified.
Tested on Satellite 6.10.0 Snap 14.0
Steps followed:
1. Have a content host registered with Satellite
2. Go to hosts > All hosts, click on Hostname.
3. Click on "Run Puppet once"
Observation:
- Puppet run is successful
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