Bug 1235335

Summary: Full steps for provisioning using boot disk from capsule missing
Product: Red Hat Satellite Reporter: Fred van Zwieten <fvzwieten>
Component: Docs Provisioning GuideAssignee: David O'Brien <daobrien>
Status: CLOSED NOTABUG QA Contact: Hayley Hudgeons <hhudgeon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: daobrien, lzap, sreber
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-24 09:45:47 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 Fred van Zwieten 2015-06-24 14:28:04 UTC
Document URL: 
https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/6.1/html/Provisioning_Guide/index.html

Section Number and Name: 
6.2

Describe the issue:
Nowhere are the full steps described that are needed to provision a host system from a capsule that is a full reversed proxy using a boot disk.

Suggestions for improvement: 
What is needed to do boot iso installations from the capsule:
1. Sync Library to the capsule (because the kickstart repo lives there)
2. Create a new installation medium with the correct URL on the capsule server
3. Add the new installation medium to the Operating System
4. Install the tftp feature on the capsule server
5. Add the tftp capsule feature to the correct subnet
6. Set up the hostgroup to use the correct content capsule, subnet and installation medium
7. Provision new host on the the hostgroup 
8. Generate the boot.iso and mount it on the host system
9. Boot the host system

Also, if token based provisioning is enabled (and it is by default) make it clear that on every rebuilt of the host system a new host boot iso must be generated, because a rebuilt will generate a new token and this token is used inside the generated boot iso

Additional information:

Comment 1 RHEL Program Management 2015-06-24 14:33:37 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 Lukas Zapletal 2015-07-24 09:45:47 UTC
I am closing this one because this will be delivered for GA: https://bugzilla.redhat.com/show_bug.cgi?id=1226814

If you have comments for the documentation please comment there. Thanks.