Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.7/html/provisioning_guide/configuring-provisioning-resources#adding-installation-media_provisioning

Section Number and Name: 

Section 2.8 Adding Installation Media to Satellite 

Describe the issue: 

Please review this email thread to get a detailed explanation.

--> http://post-office.corp.redhat.com/archives/satellite6-list/2020-November/msg00059.html 

In short, we suggest using NFS as source of installation media, but Satellite cannot work with it yet properly.

There is a semi-automatic way to get the provisioning performed but we don't have that fact highlighted there as well.


Suggestions for improvement: 

Based on the replies provided by engineering team on the thread I had highlighted before and what is mentioned here https://access.redhat.com/solutions/2674001, any of the following could help in setting up the right expectations to the customer.

1. Remove the reference of NFS from that section.

or, 

2. Include a WARNING or NOTE , that with NFS the PXE-based system deployment is untested and can only happen in a semi-automatic way i.e. one needs to copy the initrd.img and vmlinuz files from NFS source to /var/lib/tftpboot/boot with the expected names and then only pxe booting will proceed further.


Additional information: 


The following two threads might serve as a good source of information around this topic.

[satellite-tech] NFS server as the installation source for PXE-booting C
http://post-office.corp.redhat.com/archives/satellite6-list/2020-November/msg00059.html

[satellite-tech] On Satellite provision host using kickstart file from a
http://post-office.corp.redhat.com/archives/satellite-tech-list/2020-September/msg00000.html