Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionFred 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 1RHEL 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.