From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461) Description of problem: up2date fails during hardware refresh. It always uses port 80 instead of the configure port Version-Release number of selected component (if applicable): up2date-4.2.5-1 How reproducible: Always Steps to Reproduce: 1.up2date --configure 2.set a proxy on any port execpt 80 3.up2date --hardware Actual Results: Traceback (most recent call last): File "/usr/sbin/rhn_check", line 332, in ? handle_action(action) File "/usr/sbin/rhn_check", line 209, in handle_action (status, message, data) = run_action(method, params) File "/usr/sbin/rhn_check", line 164, in run_action (status, message, data) = do_call(method, params) File "/usr/sbin/rhn_check", line 92, in do_call retval = apply(method, params) File "/usr/share/rhn/actions/hardware.py", line 24, in refresh_list hardwareList = hardware.Hardware() File "hardware.py", line 517, in Hardware File "hardware.py", line 345, in read_network File "hardware.py", line 320, in findHostByRoute socket.error: (110, 'Connection timed out') Expected Results: profile updated Additional info:
this will be fixed in up2date-4.2.8 available in the next update pack
This looks good on 3U9 and 4U5 when I use a proxy on port 3128. Thus, it looks like this bug's in good shape, and I'm moving it over to CURRENTRELEASE.