Bug 592985 - passing proxy=http://url anaconda boot option does not load kickstart file
Summary: passing proxy=http://url anaconda boot option does not load kickstart file
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-17 14:36 UTC by Marcus Moeller
Modified: 2010-05-18 14:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-17 16:10:27 UTC
Type: ---

Attachments (Terms of Use)

Description Marcus Moeller 2010-05-17 14:36:35 UTC
Description of problem:

While trying to install F13 RC3 through a http proxy, kickstart file is not retrieved.

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. Boot install media, hit tab at grub menu
2. Add proxy=http://proxy.home:3128 to the kernel line
3. Hit enter and attempt to install

Actual results:
kickstart file is not retrieved

Expected results:
kickstart file should be retrieved and next stage of Anaconda should be loaded

Comment 1 Brian Lane 2010-05-17 15:16:27 UTC
If you have them, could you attach the /tmp/*log files to this? I'll try to reproduce it as well.

Comment 2 Brian Lane 2010-05-17 16:10:27 UTC
I tried this with F13 RC3 netboot iso. Passed it proxy=http://proxy.home:3128 ks=http://proxy.home/ks/f13-minimal.ks

It retrieves the ks file and stores it into /tmp/ks.cfg

Comment 3 Marcus Moeller 2010-05-18 09:02:59 UTC
In our case, we are retrieving the kickstart file from a Spacewalk server, so maybe this is an incompatibility caused by the latest Anaconda patch additions. Just thought it was a F13 client problem because F12 worked fine, even with proxy set.

Going to check on Spacewalk side, now.

Btw. thanks for trying to reproduce this issue.

Best Regards

Comment 4 Brian Lane 2010-05-18 14:38:40 UTC
A couple of things to look for:

 * Check /tmp/anaconda.log which near the top should show that it downloaded your kickstart file
 * Look at /tmp/ks.cfg which should be your kickstart file

You can do this by switching to tty2 after the GUI part of the installer has started.

Comment 5 Marcus Moeller 2010-05-18 14:48:02 UTC
Thanks for the advice, but the installation does not went that far.

Best Regards

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