Bug 1437961

Summary:	Docs need to better indicate finishing templates are for image based provisioning only
Product:	Red Hat Satellite	Reporter:	Josh Foots <jfoots>
Component:	Docs Provisioning Guide	Assignee:	Sergei Petrosian <spetrosi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Stephen Wadeley <swadeley>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.7	CC:	adahms
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Other
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-16 12:02:24 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 Josh Foots 2017-03-31 14:33:01 UTC

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/provisioning_guide/

Section Number and Name: 

Sections 6, 7, and 8

Describe the issue: 

The docs describe using finishing templates however no where is it explicitly stated that this is NOT for fresh installs. Finishing templates are for image based provisining (which makes sense when you think about how they are designed to be used) however our docs don't state this and confusion ensues. 

Suggestions for improvement: 

Add a Statement to Section 7 or 8 (or both) that explicitly states finishing templates are only designed to be used for imaged based provisioning in virtual environments. Also image != foreman discovery iso (sometimes called Foreman discovery image). Image == an install image in a virtualized environment for easy deployment.

Additional information:

Comment 1 Andrew Dahms 2017-05-07 23:55:10 UTC

Assigning to Sergei for review.

Sergei - let's add a 'Note' box to '3.3. Creating Provisioning Templates' in the Provisioning Guide where finish templates are mentioned to outline the above restriction.

Comment 5 Sergei Petrosian 2017-05-16 12:02:24 UTC

Hello
These changes are now live on the customer portal.