Description of problem: The user experience is very bad when a repo for some reason fails. The user gets no indication where the problem is, I would expect it to time out after some seconds (and it can't be interrupted with ctrl-C as reported elsewhere). [root@localhost ~]# yum -y update Loaded plugins: fastestmirror, merge-conf, presto, refresh-packagekit, remove-with-leaves Loading mirror speeds from cached hostfile rawhide/metalink | 21 kB 00:00 ^C^C^C^C^C^C^C^Z ... 14:48:49.355738 IP 192.168.2.2.38377 > 192.168.2.1.domain: 33344+ A? mirrors.rpmfusion.org. (39) 14:48:49.356028 IP 192.168.2.2.38377 > 192.168.2.1.domain: 20645+ AAAA? mirrors.rpmfusion.org. (39) 14:48:49.367242 IP 192.168.2.1.domain > 192.168.2.2.38377: 33344 2/0/0 A 213.129.242.84, A 129.143.116.10 (71) 14:48:54.355761 IP 192.168.2.2.38377 > 192.168.2.1.domain: 33344+ A? mirrors.rpmfusion.org. (39) 14:48:54.364284 IP 192.168.2.1.domain > 192.168.2.2.38377: 33344 2/0/0 A 213.129.242.84, A 129.143.116.10 (71) 14:48:54.364459 IP 192.168.2.2.38377 > 192.168.2.1.domain: 20645+ AAAA? mirrors.rpmfusion.org. (39) 14:48:54.369310 IP 192.168.2.1.domain > 192.168.2.2.38377: 20645 0/0/0 (39) 14:48:54.370727 IP 192.168.2.2.39839 > 213.129.242.84.http: Flags [S], seq 139776682, win 5840, options [mss 1460,sackOK,TS val 7026012 ecr 0,nop,wscale 6], length 0 14:48:57.370614 IP 192.168.2.2.39839 > 213.129.242.84.http: Flags [S], seq 139776682, win 5840, options [mss 1460,sackOK,TS val 7029012 ecr 0,nop,wscale 6], length 0 14:49:03.370741 IP 192.168.2.2.39839 > 213.129.242.84.http: Flags [S], seq 139776682, win 5840, options [mss 1460,sackOK,TS val 7035012 ecr 0,nop,wscale 6], length 0 14:49:15.370605 IP 192.168.2.2.39839 > 213.129.242.84.http: Flags [S], seq 139776682, win 5840, options [mss 1460,sackOK,TS val 7047012 ecr 0,nop,wscale 6], length 0 Version-Release number of selected component (if applicable): yum-metadata-parser-1.1.2-14.fc12.i686 yum-plugin-fastestmirror-1.1.23-3.fc12.noarch yum-plugin-merge-conf-1.1.23-3.fc12.noarch yum-presto-0.6.1-1.fc12.noarch yum-3.2.24-4.fc12.noarch yum-NetworkManager-dispatcher-1.1.23-3.fc12.noarch yum-plugin-remove-with-leaves-1.1.23-3.fc12.noarch yum-utils-1.1.23-3.fc12.noarch
Can you test this with the latest python-urlgrabber and yum. I think this might have been improved - maybe not fixed but better.
Same same. With a bad DNS it can't be interrupted, but eventually it times out and fails with slightly odd messages: ^C Current download cancelled, interrupt (ctrl-c) again within two seconds to exit. ^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C http://ftp.nb.lug.ro/rpmfusion/nonfree/fedora/development/i386/os/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "" Trying other mirror. http://fedora.tu-chemnitz.de/pub/linux/rpmfusion/nonfree/fedora/development/i386/os/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "" Trying other mirror. http://ftp-stud.hs-esslingen.de/pub/Mirrors/rpmfusion.org/nonfree/fedora/development/i386/os/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "" Trying other mirror. ^C^C^C^C^C^C^C yum-3.2.24-9.fc12.noarch libcurl-7.19.6-10.fc12.i686
sending this over to python to see if it can fix the ctrl-c-no-work-when-namesolving issue that's been around for a loooooooooooooong time.
*** Bug 508534 has been marked as a duplicate of this bug. ***
Seth: can you give me a minimal reproducer script (or scripts) that replicates the problems as seen by yum? I'm guessing that the reproducer is a one-liner, but if I'm going to attack this from underneath (the C side), it'd be useful to know _exactly_ how it looks from the yum and .py side. Thanks.
try resolving a hostname on a system which has network connectivity but cannot reach it's nameservers for whatever reason. try to ctrl-c it.
Actually I think with the move to urlgrabber using curl, the name lookup might be just from inside libcurl now. At least "grep gethostby" doesn't return any matches inside yum, and the two inside urlgrabber should be dead code.
pretty sure we have a couple of urllib calls remaining that may hit it internally.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.