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.

Created attachment 1487590 [details]
screen shot as provided by the customer

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/provisioning_guide/index#Configuring_Provisioning_Resources-Creating_Provisioning_Templates-Deploying_SSH_Keys_during_Provisioning

Section Number and Name: 3.5.1. Deploying SSH Keys during Provisioning

Describe the issue: TOC is only partially generated and the MarkDown is not processed past chapter 3.
This is for all single/multi page and PDF versions.
The document shows "<<<<<<< HEAD . Create a new host that is associated with the provisioning template or rebuild a host using the OS associated with the modified template. For more information, see Section 3.5.1, “Deploying SSH Keys during Provisioning”. " Which points to some discrepancy in the documentation. Also thereafter every topic is mention as

=== Creating Compute Profiles 
=== Creating an Activation Key
=== Setting a Default Encrypted Root Password for Hosts..and so on

Suggestions for improvement: 

Additional information:

Thank you for raising this bug.

These changes are now live on the Customer Portal 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/provisioning_guide/#Configuring_Provisioning_Resources-Creating_Provisioning_Templates-Deploying_SSH_Keys_during_Provisioning

Updated release flags.