Bug 724151

Summary:	Network down after live installation
Product:	[openSUSE] openSUSE 12.1	Reporter:	Ralf Haferkamp <ralf>
Component:	Installation	Assignee:	Marius Tomaschewski <mt>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	fcrozat, forgotten_7pwnVrOCb1, freek, gs, martin.schlander, mvidner
Version:	Beta 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	/var/log/messages after starting installed system YaST logs after installation

Description Ralf Haferkamp 2011-10-14 09:55:37 UTC

After the live installation is finished (including the auto configuration) and YaST starts the installed system I don't have an IP Address anymore. It seems something took down all interfaces.

I seems this problem is present regardless of whether I use NetworkManager or ifup based setup.

Note: I don't know if this is related, but I choose to setup LDAP authentication during installation.

Rebooting the machine fixes the problem.

Logfiles will follow.

Comment 1 Ralf Haferkamp 2011-10-14 09:56:23 UTC

Created attachment 456582 [details]
/var/log/messages after starting installed system

Comment 2 Ralf Haferkamp 2011-10-14 09:56:57 UTC

Created attachment 456583 [details]
YaST logs after installation

Comment 4 Marius Tomaschewski 2011-10-19 12:35:58 UTC

I think this is a dup of bnc#719214 -- there are 2 dhcpv4 clients
(dhclient + dhcpcd) clients and also ModemManager (=NM) running
as far as I see in attachment from comment 1.

Ralf, please reopen when it happens again with newer versions.

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

Comment 5 Freek de Kruijf 2011-10-24 13:28:19 UTC

It is still present in RC1 with KDE Live CD. Immediately after the first reboot there is no network, only lo. A 'rcnetwork start' as root in a terminal starts the network. It is generated as an ifup type network.

Comment 6 Martin Schlander 2011-10-24 17:41:43 UTC

For me on beta and rc1 KDE liveusb installations (installed from running desktop), on the first systemstart after the "autoconfiguration", plasmoid-networkmanagement complains cuz NetworkManager is not running.

After a reboot or a restart of the network service, things work as they should.

Comment 7 Freek de Kruijf 2011-10-24 18:31:14 UTC

Also after a NET installation and after the first reboot, the network has not been started. Hence the software update fails, unless the network has been started by hand.

Comment 8 Forgotten User 7pwnVrOCb1 2011-10-25 18:38:16 UTC

Also after a harddisk installation of self made openstudio livecds based on 11.4
plus updates.
the livecd did never have a dhcp problem, but every time after installation. 
It`s not a new problem.

Comment 9 Marius Tomaschewski 2011-10-27 08:47:09 UTC

I think this is either the same problem as in bug 725405 or the yast2
2nd stage makes something strange.

Comment 10 Marius Tomaschewski 2011-10-27 14:08:04 UTC

Martin,

do you know what goes wrong in 2nd state? AFAIR yast2 is using own scripts
to start network while a "boot" of the installed system.

Comment 11 Martin Vidner 2011-11-01 13:48:19 UTC

I think this is a buplicate of bnc#726823

Comment 12 Martin Vidner 2011-11-01 13:48:50 UTC

DWIM

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

Comment 13 Martin Schlander 2011-11-06 11:08:57 UTC

Just did a dvd installation of RC2. 

Same deal. On first boot NetworkManager is not running, making the plasmoid throw an error.

After reboot everything is fine.