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.

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html-single/provisioning_guide/index#Configuring_Provisioning_Resources-Using_Kickstart_Repository_as_Installation_Medium

Section Number and Name: 

3.4. Using a Synced Kickstart Repository for a Host’s Operating System

Describe the issue: 

To provision a RHEL-8 host, we need to Sync and add the following repositories to the Content View and publish it and also Content View needs to be promoted when using a different LifeCycle Environment other than Library.

Red Hat Enterprise Linux 8 for x86_64 - AppStream Kickstart x86_64 8
Red Hat Enterprise Linux 8 for x86_64 - BaseOS Kickstart x86_64 8

If one of the repositories is not available/included in the Lifecycle environment and content view then provisioning will fail.

Suggestions for improvement: 

Add a note in the standard provisioning documentation to include both the repositories, If one of the repositories is not available/included in the Lifecycle environment and content view then provisioning will fail.

Additional information:

Hi there, 

Documentation about syncing repos is taken care of in the Content Management Guide, which is linked to in all the prerequisites of all the different provisioning options in the Provisioning Guide. 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6-beta/html/content_management_guide/importing_red_hat_content#Importing_Red_Hat_Content-Selecting_Red_Hat_Repositories_to_Synchronize

I will add a link to this article to the prerequisites. In the meantime, please feel free to share the link with the customer. 

Thanks, 

Melanie

These changes are now live on the customer portal: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html/provisioning_guide/configuring_provisioning_resources#Configuring_Provisioning_Resources-Using_Kickstart_Repository_as_Installation_Medium

Thanks, 

Melanie