Bug 462675 - Enabling IPv6 in YaST Breaks Update: "Couldn't Resolve Host"
Summary: Enabling IPv6 in YaST Breaks Update: "Couldn't Resolve Host"
Status: RESOLVED DUPLICATE of bug 441947
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.1
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-28 14:41 UTC by Forgotten User JtaKqlU8J9
Modified: 2009-01-21 18:32 UTC (History)
0 users

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User JtaKqlU8J9 2008-12-28 14:41:46 UTC
By default, IPv6 is enabled in YaST Network Devices (as it should be). When running openSUSE 11.1 final, all YaST software modules requiring checking online repositories were broken. Disabling IPv6 in Network Devices allowed zypper to find repositories. 

This behavior existed in several betas running openSUSE 11.1 in a VirtualBox VM, but also in the final release on my x86_64 desktop, all using the same 2WIRE router. 

To reproduce:

1. Install openSUSE 11.1.
2. Go to YaST > Software > Software Repositories (actually any of the Software modules except Media Check will do)
3. When trying to connect to each online repository, this message will appear:

Download (curl) error for
 'http://download.opensuse.org/distribution/11.1/repo/non-
 oss/repodata/repomd.xml':
 Error code:
 Error message: Couldn't resolve host 'download.opensuse.org'

4. Go to YaST > Network Devices > Network Settings.
5. Disable IPv6.
6. Reboot.
7. Repeat Step 2. YaST connects to all repositories, can add Community Repositories, and update/install software.
Comment 1 Andreas Jaeger 2009-01-19 09:06:58 UTC
This looks to be like a duplicate of #441947.  Could you check whether that's correct, please?
Comment 2 Forgotten User JtaKqlU8J9 2009-01-19 14:49:29 UTC
Andreas,

Yes, certainly sounds the same. I will test the proposed fix on my two machines (x86 and 86_64) tonight.
Comment 3 Andreas Jaeger 2009-01-21 11:32:28 UTC
Mike, if the fix helps, please close this bug as duplicate of #441947.
Comment 4 Forgotten User JtaKqlU8J9 2009-01-21 18:32:33 UTC
Yes, the fix helped. We can close this, and I am doing that.

*** This bug has been marked as a duplicate of bug 441947 ***