Bug 1325117

Summary: anaconda --help - insufficient --ks description
Product: [Fedora] Fedora Reporter: Jaroslav Škarvada <jskarvad>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 19:52:17 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:

Description Jaroslav Škarvada 2016-04-08 10:08:20 UTC
Description of problem:
There is written the following:

--ks  Gives the location of the kickstart file to be used for installation.
        The KICKSTART_URL supports fetching kickstarts from HTTP/S, FTP, NFS,
        from a local file, from a local harddrive, from an optical disk and from
        BIOS RAID sets. For details on the KICKSTART_URL syntax see the Anaconda
        options wiki page: http://fedoraproject.org/wiki/Anaconda_Boot_Options

Not counting that the URL http://fedoraproject.org/wiki/Anaconda_Boot_Options is obsoleted, but I was able to get to the Boot Options description, the main problem is that I wasn't able to find what the KICKSTART_URL is and where to specify it. From the description I thought I could do something like:

# anaconda --ks KICSTART_URL

but I cannot. So it seems there is a room for improvement of the --ks description

Version-Release number of selected component (if applicable):
anaconda-23.19.10-1.fc24.x86_64

How reproducible:
always

Steps to Reproduce:
1. anaconda --help | grep -A 4 -- --ks

Actual results:
Not clear instructions how to specify kickstart URL.

Expected results:
Clear instructions how to specify kickstart URL.

Additional info:

Comment 1 Jaroslav Škarvada 2016-04-10 11:22:09 UTC
I guess it should work the following way:
# anaconda --ks=KICSTART_URL

but unfortunately the argparse doesn't take the second (KICKSTART_URL) argument, i.e.:

# anaconda --ks=http://localhost/ks.cfg
...
anaconda: error: argument --ks: ignored explicit argument 'http://localhost/ks.cfg'

# anaconda --ks http://localhost/ks.cfg
...
anaconda: error: unrecognized arguments: http://localhost/ks.cfg

Comment 2 David Shea 2016-04-11 12:05:17 UTC
--kickstart=<filename> takes a filename argument. --ks does not take an argument, and its documentation needs to be fixed.

However, --kickstart only accepts local files. You will need to fetch kickstart files from the network before passing them to the CLI.

Comment 3 Fedora End Of Life 2016-11-25 07:17:45 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2016-12-20 19:52:17 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.