Bug 147270

Summary:	network not setup.
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Marcus Meissner <meissner>
Component:	Installation	Assignee:	Martin Vidner <mvidner>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Blocker
Priority:	P5 - None	CC:	suse-beta
Version:	Beta 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	yast2logs.tar.bz2

Description Marcus Meissner 2006-02-01 15:33:38 UTC

i did a regular install, network configured with just next-> 

now eth0 is not brought up, ifup eth0 says:
"No configuration found for eth0".

Comment 1 Marcus Meissner 2006-02-01 15:35:07 UTC

Created attachment 66042 [details]
yast2logs.tar.bz2

/var/log/YaST2/y2log*

Comment 2 Martin Vidner 2006-02-01 16:18:26 UTC

You did not just click next. You toggled NetworkManager on and off.
The bug is triggered by changing the NM status in the proposal screen.

Comment 3 Marcus Meissner 2006-02-01 16:21:23 UTC

yes, i was curious. (should have mentioned it)
would it have changed anything if i left it as is?


also, isnt NM be the default now?

Comment 4 Martin Vidner 2006-02-01 16:30:58 UTC

Yes, if you don't touch it, it will be fine.

For SL, NM is on for laptops.

Comment 5 Christian Zoz 2006-02-03 08:49:23 UTC

And if you decide not to use NM you end up with not working interface. This bug is exactly a duplicate of bug 144665.

Comment 6 Martin Vidner 2006-02-05 19:13:18 UTC

No. That bug is that something is proposed when you would like something else to be proposed. In this one what is proposed is not written to the disk. Quite different.

Fixed in yast2-network-2.13.21.

Comment 7 Martin Vidner 2006-02-06 08:26:21 UTC

DWIM, Bugzilla.