Bug 1977282

Summary:	Page breaks with "No template mapped to feature Run Puppet Once" error while trying to run puppet on host from Satellite.
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	Remote Execution	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	sganar
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	akjha, aruzicka, lstejska, pcreech, tbrisker
Target Milestone:	6.10.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_remote_execution-4.5.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:12:12 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 Jameer Pathan 2021-06-29 11:38:52 UTC

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:

Comment 2 Brad Buckingham 2021-07-01 14:34:12 UTC

Is this a regression from 6.9?

Comment 3 Jameer Pathan 2021-07-02 06:16:18 UTC

yes, I don't see this issue on 6.9.3

Comment 4 Tomer Brisker 2021-07-06 08:36:32 UTC

Moving to remote execution for further investigation

Comment 6 Tomer Brisker 2021-07-07 08:33:59 UTC

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

Comment 7 Adam Ruzicka 2021-07-07 08:39:14 UTC

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

Comment 9 sganar 2021-08-23 14:58:34 UTC

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

Comment 12 errata-xmlrpc 2021-11-16 14:12:12 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