Bug 443217 - YaST2 gives 2 errors per repository when I reconfigure my ethernet
Summary: YaST2 gives 2 errors per repository when I reconfigure my ethernet
Status: RESOLVED DUPLICATE of bug 401966
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: i686 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Ladislav Slezák
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-09 20:57 UTC by Out of Control
Modified: 2008-11-14 12:03 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 Out of Control 2008-11-09 20:57:59 UTC
I originally put my report in bug 387050, but the assignee punted. Here's the cut and paste:

------
When I configure my LAN, which does not access the internet, I get an error
message for each online repository that can't be reached. Actually, I get 2
error messages per repo:

Download failed:
Download (curl) error for
'http://download.opensuse.org/distribution/11.0/repo/oss/content':
Error code: Connection failed
Error message: Couldn't resolve host 'download.opensuse.org'

and

Cannot access installation media
(Medium 1)
Check whether the server is accessible.

Do I really deserve 8 error messages for changing my ipaddress? I have
configured correctly, but network settings is bombarding me with errors,
because it really wants to access the repos right now!

This should fail silently. Give errors when the repos are required for the user
initiated action. I shouldn't need internet access to reconfigure my NIC.
------
The yast2 version is yast2-network 2.16.48-3.1
The NetworkManager version is 0.7.0.r3685-7.2

This does not happen if I select ifup to manage the connection in global options, only when NetworkManager is managing the connection. All it appears to download when a wan connection is available is the metadata. Whatever it's trying to do, it's an optional step, and I'd like to get past it without all the errors.
Comment 2 Ladislav Slezák 2008-11-14 12:03:54 UTC
Fixed in 11.1

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