Bug 2127934

Summary:	rex pull-provider client not configured during host provisioning
Product:	Red Hat Satellite	Reporter:	Peter Ondrejka <pondrejk>
Component:	Provisioning Templates	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.12.0	CC:	ahumbe, aruzicka, mhulan
Target Milestone:	6.12.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-3.3.0.17-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-16 13:35:50 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 2022-09-19 12:10:38 UTC

Description of problem:

Provisioning a host with enable-remote-execution-pull parameter does not enable the yggdrasil client as expected.

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

Satellite 6.12 snap 10, provisioning rhel8 host

How reproducible:
always

Steps to Reproduce:
1.Provision a host with enable-remote-execution-pull parameter, make sure client repo is available in host's lce

Actual results:
Host is provisioned correctly but the client is not configured. On the host, 
original-ks.cfg shows no trace of setup being executed. It seems that the 'remote_execution_pull_setup' snippet is not triggered from the Kickstart default finish template. However, if I preview the finish template for the host, the template is rendered with the snippet.

Expected results:
Yggdrasil client properly configured

Additional info:

Comment 2 Peter Ondrejka 2022-10-10 14:15:05 UTC

Verified on Sat 6.12 snap 14 using satqe automation. The host provisioned with enable-remote-execution-pull parameter has now yggdrassil client properly configured and rex jobs succeed

Comment 6 errata-xmlrpc 2022-11-16 13:35:50 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 (Important: Satellite 6.12 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-2022:8506