Bug 1369209

Summary:	Satellite builds broken puppet modules from Configuration Channel Content
Product:	Red Hat Satellite	Reporter:	Taft Sanders <tasander>
Component:	Transitions	Assignee:	Adam Price <adprice>
Status:	CLOSED WONTFIX	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, jbhatia, jcallaha, xdmoon
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-15 15:00:54 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:

Description Taft Sanders 2016-08-22 16:34:14 UTC

Description of problem:
Configuration files from Satellite 5 are imported into Satellite 6 as puppet modules. The puppet modules break when referencing the file associated with the puppet module.

Version-Release number of selected component (if applicable):
Satellite 6.2.0
Puppet 3.8.6-2

How reproducible:
Everytime

Steps to Reproduce:
1.Transistion files from Satellite 5 to Satellite 6 using the documentation (https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/transition-guide/35-importing-to-satellite-6)
2.Apply puppet module to client system
3.Watch errors

Actual results:
Error: /Stage[main]/Common_file_6/File[etcissue.net]: Could not evaluate: Could not retrieve information from environment KT_DNB_Library_Puppet_Config_Modules_7 source(s) puppet:///modules/dnb-common_file_6/etcissue.net

Expected results:
Puppet to apply/build resource file


Additional info:
Workaround found is to rebuild puppet modules using the content variable in the puppet module to point to the file.

Comment 4 Bryan Kearney 2017-08-15 15:00:54 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.