Bug 535837

Summary:	choosing Network Manager during install fails initial Inet test, re-work choice to not install, it is installed
Product:	[openSUSE] openSUSE 11.2	Reporter:	John Pemberton <Pemberton.John.M>
Component:	Installation	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	coolo, pearson45j, stsymbal
Version:	Milestone 5
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Yast logs

Description John Pemberton 2009-09-01 06:13:56 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.4 Firefox/3.5.2

New install selected, from images, choosing KDE.

Normally I use standard ifconfig, route, netstat, etc., to manage networking.  Just for a change I thought I'd ask for Network Manager, so requested it during initial installation.  Seemingly the system couldn't pass the initial network test with that selection.  Retried repeatedly and it failed the test each time.  Used back button to change selection to standard networking handling, then the test passed.  If it can't be used for initial installation, perhaps
Network Manager shouldn't be a choice at that time.  Also, when install finished, even though I changed ny installation choice, de-selecting Network Manager, I discovered that it had been installed anyway, even though the system appears to be configured not to use it.


Reproducible: Didn't try

Steps to Reproduce:
Please see details section.  I didn't repeatedly re-install.  So I can only report what happened the one time I tried it.

Comment 1 Shuang Qiu 2009-09-11 06:24:07 UTC

Could you please attach y2logs according to http://en.opensuse.org/Bugs/YaST?
Thanks!

Comment 2 John Pemberton 2009-09-15 06:07:42 UTC

Created attachment 318232 [details]
Yast logs

Adding log files currently in /var/log/YaST2 and sub-dir(s).

Comment 3 John Pemberton 2009-09-15 06:13:48 UTC

I had occasion to re-install M6 - the same thing happened.

Comment 4 Michal Zugec 2009-10-20 13:17:16 UTC

1 - 

settings into NetworkManager $[
     "exit":0,
     "stderr":"\n** (/usr/lib/NetworkManager/nm-opensuse-sysconfig-merge:6079): WARNING **: Ignoring invalid IP4 address: invalid prefix: '0'\n\n** (/usr/lib/NetworkManager/nm-opensuse-sysconfig-merge:6079): WARNING **: parse_ifcfg: Invalid connection for ra0: 'NMSettingWireless' / 'ssid' invalid: 2\n\n** (/usr/lib/NetworkManager/nm-opensuse-sysconfig-merge:6079): WARNING **: Ignoring invalid IP4 address: invalid prefix: '0'\n",
     "stdout":"Converting 'ifcfg-ra0' (interface: ra0: type: 2)\nConverting 'ifcfg-eth0' (interface: eth0: type: 1)\n"
]
2009-09-13 17:19:20 <5> toe-heaven(3078) [YCP] Lan.ycp:415 virt_net_proposal false
2009-09-13 17:19:21 <3> toe-heaven(3078) [bash] ShellCommand.cc(shellcommand):78 ..dead..dead


But - because of BOOTPROTO='dhcp', there is empty IPADDR and no PREFIXLEN


2 - NetworkManager, NetworkManager-kde4 was installed in 1st stage as part of KDE4 pattern

Comment 5 Michal Zugec 2009-10-20 13:21:24 UTC

Tambet, it seems that NM didn't connect internet via plugged eth0

Comment 6 Michal Zugec 2009-10-21 12:58:03 UTC

Reproduced. Network is up but Internet test failed because ifstatus reported code 3 (interface is under NetworkManager control) which is changed sysconfig behavior against 11.1.
Coolo, will tou accept fixed (yast2.rpm) package into 11.2?

Comment 7 Michal Zugec 2009-10-21 13:08:09 UTC

Anyway, fixed in factory (yast2-2.18.27)

Comment 8 Stephan Kulow 2009-10-21 13:12:45 UTC

yes.

Comment 9 Michal Zugec 2009-10-21 13:42:25 UTC

ok, FIXED then

Comment 10 Katarina Machalkova 2009-10-27 09:47:26 UTC

*** Bug 545687 has been marked as a duplicate of this bug. ***