Bug 1228748 - Installation media lets you specify a nfs path but doesn't format it properly for a RHEL kickstart
Summary: Installation media lets you specify a nfs path but doesn't format it properly...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.1.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Ondřej Pražák
QA Contact: Radovan Drazny
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1287901
TreeView+ depends on / blocked
 
Reported: 2015-06-05 15:01 UTC by Jacob Hunt
Modified: 2020-06-11 12:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:02:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 992 0 Normal Closed Unspported scheme - when using nfs path for installation media. 2020-11-09 20:15:56 UTC

Description Jacob Hunt 2015-06-05 15:01:26 UTC
Description of problem:

The installation media path says you can specify an NFS server and when you enter the path, it requires it be formatted as 'nfs://server/path'. The resulting kickstart has a url defined in the format:

url --url nfs://server/path

The above syntax is not valid for RHEL 6 (and possibly RHEL 7) so the kickstart fails. 

The proper syntax for a nfs installation source is:

nfs --server=<server> --dir=<path> --opts=<options>

Satellite should properly format the nfs path if it is allowing one to be specified or it should request the proper data to construct the nfs kickstart options.

Comment 2 RHEL Program Management 2015-06-05 15:12:45 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 David O'Brien 2015-08-19 02:43:35 UTC
Can I get some suitable doc text for a rel note for this?

thanks

Comment 8 Ohad Levy 2016-03-16 09:28:23 UTC
Connecting redmine issue http://projects.theforeman.org/issues/992 from this bug

Comment 9 Bryan Kearney 2016-03-16 10:11:05 UTC
Upstream bug component is Capsule

Comment 11 David O'Brien 2016-04-18 00:48:57 UTC
Reset docs contact <> daobrien

Comment 18 Satellite Program 2017-03-23 16:11:24 UTC
Upstream bug assigned to oprazak

Comment 19 Satellite Program 2017-03-23 16:11:28 UTC
Upstream bug assigned to oprazak

Comment 20 Satellite Program 2017-04-07 12:11:36 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/992 has been resolved.

Comment 22 Radovan Drazny 2017-09-21 14:50:34 UTC
Tested on Satellite 6.3, foreman-1.15.3.2-1.el7sat.

1. Created a custom installation media with "nfs://<server>/<path>/<to>/<directory>" path. 
2. Created a custom Operating system with the RedHat family type and with the Installation media from the step 1 assigned
3. Created a host, and assigned the Operating system from the step 2 to it.
3. Checked the resulting Provisioning template for the newly created system. nfs line was correctly formatted as "nfs --server <server> --dir /<path>/<to>/<directory>""

Comment 23 Bryan Kearney 2018-02-21 17:02:21 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336


Note You need to log in before you can comment on or make changes to this bug.