Bugzilla – Bug 533546
zypper behavior when ipv6 is inaccessible
Last modified: 2009-08-23 09:30:16 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.4 Firefox/3.5.2 I am running opensuse 11.2 milestone6 KDE4 LiveCD when I try # zypper refresh Retrieving repository 'openSUSE-11.2-Non-Oss' metadata [\]Failed to download /media.1/media from http://download.opensuse.org/distribution/11.2/repo/non-oss/ Abort, retry, ignore? [a/r/i/?] (a): It says 'Failed to download' but actual problem isn't connected with downloading. Let consider what actually happens when zypper tries to download the file. IPv6 is enabled by default in LiveCD, but my network provider provides only IPv4 networking(but provides IPv6 DNS). We can get to know from logs that zypper uses aria2c # aria2c http://download.opensuse.org/distribution/11.2/repo/non-oss/media.1/media 2009-08-22 13:51:52.144299 WARN - You may encounter the certificate verification error with HTTPS server. See --ca-certificate and --check-certificate option. 2009-08-22 13:51:52.522897 ERROR - CUID#6 - Download aborted. URI=http://download.opensuse.org/distribution/11.2/repo/non-oss/media.1/media Exception: [AbstractCommand.cc:195] URI=http://widehat.opensuse.org/factory-snapshot/repo/non-oss/media.1/media -> [SocketCore.cc:287] Failed to connect to the host 2a01:138:a004:0:21a:a0ff:fe26:efa9, cause: all addresses failed It tried to use IPv6 address and it failed. The first issue is that zypper failure message isn't informative. I suppose that zypper doesn't know where is the problem itself. The second issue is that aria2c or zypper have to try to use IPv4. AFAIK the only one way to make aria2c to use IPv4 is to disable IPv6 on boot, but there are no any hints how to do. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Did you read/try http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.2_dev ? * Downloads/updates with aria/metalink support will fail, work-around: "export ZYPP_ARIA2C=0" (Bug #532575)
I think It should be marked as DUPLICATE. *** This bug has been marked as a duplicate of bug 532575 ***