Bug 183230 - system-config-kickstart doesn't work with a proxy
Summary: system-config-kickstart doesn't work with a proxy
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-kickstart
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
: 186232 (view as bug list)
Depends On: 185309
TreeView+ depends on / blocked
Reported: 2006-02-27 17:01 UTC by oll
Modified: 2008-08-02 23:40 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2006-11-21 15:59:21 UTC

Attachments (Terms of Use)

Description oll 2006-02-27 17:01:14 UTC
Description of problem:

system-config-kickstart doesn't start.
It seems to be a proxy problem since strace tells me it blocks to :

connect(3, {sa_family=AF_INET, sin_port=htons(80),
sin_addr=inet_addr("")}, 16 <unfinished ...>

Setting the http_proxy variable doesn't help (I'm pretty sure I have the right
http_proxy setting since pirut and yum work well with it)

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

FC5-test3 with the latest "yum update" (execept for kernel)


How reproducible:

Comment 1 oll 2006-02-27 17:02:22 UTC
Just forgot to add that I'm indeed behind a proxy.

Comment 2 Chris Lumens 2006-03-22 15:00:21 UTC
*** Bug 186232 has been marked as a duplicate of this bug. ***

Comment 3 Chris Lumens 2006-03-24 16:18:26 UTC
Can you confirm that pirut and yum are working, then immediately try
s-c-kickstart and verify it is not working with the same settings?  I'm getting
conflicting reports about the quality of yum's proxy support right now.

Comment 4 stef 2006-03-27 07:12:56 UTC
pirut and yum are NOT working for me.

for yum I have to do this to make it work :
[stranche@yuri ~]$ sudo su -
[root@yuri ~]# !export
export http_proxy=http://proxy:8080
[root@yuri ~]# yum -y upgrade

the line proxy=http://proxy:8080  is present in /etc/yum.conf

for pirut I can't have a working case since the sudo destroy the environnement
variable wich says X is running

[stranche@yuri ~]$ sudo su
[root@yuri stranche]# pirut
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Unable to import modules.  Maybe you're not running under X?

all this seems related to problem encountered in Bug 186054 

Comment 5 oll 2006-03-27 07:24:08 UTC
I just check and for me, yum and pirut work perfectly (with the right http_proxy
variable set)
But s-c-k don't

This is an official FC5 with a fresh yum update (system-config-kickstart-2.6.6-2)

Comment 6 stef 2006-03-27 07:29:24 UTC
(In reply to comment #5)
> I just check and for me, yum and pirut work perfectly (with the right
http_proxy variable set)

so basicaly this means that as for my case even if proxy=http://proxy:8080  is
present in /etc/yum.conf, you still have to do export
http_proxy=http://proxy:8080 in the console you're running to make it work, right ?

Comment 7 oll 2006-03-28 14:54:34 UTC
Until now, I always the http_proxy variable to make it work.
I just tested unsetting http_proxy and adding proxy=http://myproxy:myport in
/etc/yum.conf and , indeed , it doesn't work.
But I'm not sure of the syntax either, since the man page is not very precise
about it.

Comment 8 James Martin 2006-04-04 16:19:52 UTC
I'm having the same problem here.. shouldn't the bug be changed to reflect that
it occurs on fc5 and not just fc5test3?

Comment 9 Chris Lumens 2006-09-15 15:28:13 UTC
Is this still a problem with FC6test3?  s-c-kickstart isn't doing anything
special with yum or networking here, so any proxy problem should be in yum
itself.  There have been a lot of releases since this bug was filed so it's
possible it has been fixed upstream.

Comment 10 James Martin 2006-11-21 14:36:20 UTC

Seems to work now on FC6.. So long as the http_proxy environment variable is set
or the proxy is defined in gnome.

Comment 11 Chris Lumens 2006-11-21 15:59:21 UTC
Thanks for the confirmation.  I'm closing on the basis of comment #10.  It seems
like we should have a better setup for defining proxies for yum in general, but
yum configuration issues are a whole different bug.

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