Bug 1690204

Summary:	[RFE] merge the upstream Foreman Userdata plug-in into Satellite
Product:	Red Hat Satellite	Reporter:	matt jia <mjia>
Component:	Compute Resources - VMWare	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED ERRATA	QA Contact:	Sanket Jagtap <sjagtap>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.4.0	CC:	bkearney, chrobert, mhulan, rjerrido, sjagtap
Target Milestone:	6.6.0	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 12:47:16 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 matt jia 2019-03-19 01:49:21 UTC

Description of problem:

In this post, it describes how to use provision VMWare using userdata via Satellite 6.3. However, the upstream Foreman Userdata plug-in is not merged into Satellite and cause this solution is not fully supported by us.

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

6.4

How reproducible:

Easy

Steps to Reproduce:

the upstream Foreman Userdata plug-in is not in any Red Hat repo.

Actual results:

the upstream Foreman Userdata plug-in is not shipped by Red Hat.

Expected results:

the upstream Foreman Userdata plug-in should be shipped by Red Hat.

Additional info:

Comment 4 matt jia 2019-03-19 01:56:57 UTC

The post is here:

https://access.redhat.com/blogs/1169563/posts/3640721

Comment 6 Bryan Kearney 2019-04-29 16:07:19 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24881 has been resolved.

Comment 7 Marek Hulan 2019-04-30 10:35:04 UTC

There's in fact also part on smart proxy which is not merged yet.

Comment 8 Bryan Kearney 2019-06-18 14:08:07 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24881 has been resolved.

Comment 16 Sanket Jagtap 2019-07-18 13:02:07 UTC

Build : Satellite 6.6 snap 11


I was able to provision and install the Vm on VMware with cloud init successfully following the above blogpost

2019-07-17 08:40:00,099 - url_helper.py[DEBUG]: [0/11] open 'http://sat-host/unattended/built?token=5398f5ce-95ab-4ee9-ac04-881dc4d3e24d' with {'url': 'http://sat-host/unattended/built?token=5398f5ce-95ab-4ee9-ac04-881dc4d3e24d', 'headers': {'User-Agent': 'Cloud-Init/18.2'}, 'allow_redirects': True, 'method': 'GET', 'timeout': 5.0} configuration
2019-07-17 08:40:01,201 - url_helper.py[DEBUG]: Read from http://sat-host/unattended/built?token=5398f5ce-95ab-4ee9-ac04-881dc4d3e24d (201, 0b) after 1 attempts
2019-07-17 08:40:01,202 - handlers.py[DEBUG]: finish: modules-final/config-phone-home: SUCCESS: config-phone-home ran successfully
2019-07-17 08:40:01,202 - main.py[DEBUG]: Ran 5 modules with 0 failures

Comment 17 Sanket Jagtap 2019-07-18 13:15:46 UTC

See Also: https://bugzilla.redhat.com/show_bug.cgi?id=1731155

Comment 20 errata-xmlrpc 2019-10-22 12:47:16 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, 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-2019:3172