Bug 1896771

Summary: NFS based installation media can only be used in Semi-Automatic mode in Satellite 6.7
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: ProvisioningAssignee: Zuzana Lena Ansorgova <zuansorg>
Status: CLOSED CURRENTRELEASE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: medium    
Version: 6.7.0CC: ehelms, lstejska, ryandeussing, sshtein, zuansorg
Target Milestone: UnspecifiedKeywords: Documentation, EasyFix, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard: provisioning-guide
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-22 18:20:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sayan Das 2020-11-11 14:13:13 UTC
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

Comment 6 Brad Buckingham 2023-05-08 12:47:51 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 8 Brad Buckingham 2023-06-12 23:15:45 UTC
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation.

Comment 9 Zuzana Lena Ansorgova 2024-01-15 16:57:18 UTC
https://github.com/theforeman/foreman-documentation/pull/2678