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.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html-single/provisioning_guide/

Section Number and Name: 
Probably somewhere here:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html-single/provisioning_guide/#Provisioning_Bare_Metal_Hosts-Creating_New_Hosts_with_PXE-less_Provisioning

Describe the issue: 
No mention about token_duration in provisioning guide

Suggestions for improvement: 

Satellite 6 offers a security feature in accessing ISO images being loaded by pxelinux.0 binary to the booting host. For each individual host to be kick-started, Satellite generates unique token that needs to be provided in URL of the iso image to be downloaded. Generating and providing of this token is done automatically via Satellite and TFTP server.

Validity of this token is X minutes by default in Satellite 6.0 and 360 minutes from Satellite 6.1 onwards. This time out is adjustable via token_duration (Administer => Settings => Provisioning) option. Therefore, reboot of the host shall be performed within configured time frame , since creating the host in Satellite for provisioning.

The token_duration can be disabled by setting it to 0

Additional information:

Thank you for raising this bug.

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/provisioning_guide/provisioning_bare_metal_hosts#Provisioning_Bare_Metal_Hosts-Security_Token_in_the_Boot_Process

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/provisioning_guide/provisioning_bare_metal_hosts#Provisioning_Bare_Metal_Hosts-Security_Token_in_the_Boot_Process