Bug 105691

Summary:	Upgrade SL10B1 to SL10B2 renders eth0 unuseable.
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Martin Mewes <novell>
Component:	YaST2	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED NORESPONSE	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Major
Priority:	P5 - None	CC:	novell
Version:	Beta 2
Target Milestone:	---
Hardware:	i586
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Martin Mewes 2005-08-18 21:42:44 UTC

I did a standard upgrade scenario upgrading from SL10B1 to SL10B2.
YaST2 installs an additional eth1 instead of using the installed eth0.
You then need to delete eth0 in YaST2 later, go out of YaST2, return to the
network config and then the shown prior network card eth1 is eth0 again.

Please see http://www.opensuse.org/index.php/User:Macmewes/VMware for details
and screenshots.

Comment 1 Arvin Schnell 2005-08-19 07:00:25 UTC

Please provide YaST2 logs and hwinfo output, see:
http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST

Comment 2 Lukas Ocilka 2005-09-02 07:40:24 UTC

Martin, please see this bug whether you are able to do anything without logs. If
you are unable to do anything, close it with "no logs, no fix". Thanks.

Comment 3 Martin Vidner 2005-09-02 10:18:52 UTC

Indeed, I have run out of crystal balls so the logs are necessary. Screenshots 
sometimes help but not in this case.

Comment 4 Martin Mewes 2005-09-03 13:05:39 UTC

(In reply to comment #3)
> Indeed, I have run out of crystal balls so the logs are necessary. Screenshots 
> sometimes help but not in this case. 
>  

Right now I am not able to send in any logs because of data loss,
I change this bug to LATER in order to do the step again from SL10B3 to SL10B4
and see what happens.

Comment 5 Martin Vidner 2006-08-28 11:34:23 UTC

Reassigning to the new maintainer of yast2-network.

Comment 6 Michal Zugec 2007-11-21 13:52:58 UTC

No logs for really looooong time