Bug 307162

Summary:	NIC incorrectly configured at install time
Product:	[openSUSE] openSUSE 10.3	Reporter:	tim chappell <laptop>
Component:	Installation	Assignee:	Michal Zugec <mzugec>
Status:	VERIFIED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Critical
Priority:	P2 - High	CC:	fbourdonnec, jdsn
Version:	Beta 2
Target Milestone:	---
Hardware:	i586
OS:	openSUSE 10.3
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	dmesg.txt ifconfig failing report /var/log files at failing point lspci output dmesg of working boot ifconfig working report tar.gz containing /var/log, dmesg and ifconfig at various points.

Description tim chappell 2007-09-03 13:01:05 UTC

At first install when trying to configure the Ethernet cards (3 fitted; one builtin, 2 pci) yast displays the Ethernet nics in the following order:
Eth0 – 3com
Eth1 - realtek
Eth2 – reported as HP onboard device (Intel)

The onboard device (eth2) is selected and configured as static IP since this is the connected device. However this fails the connectivity test (curl) – I should mention that this is via a proxy, but the failure is to find a DNS server (which was correctly specified) and once the ethernet device begins working none of the proxy networking parameters require further change.

Continuing with the install is otherwise successful. 

Attached are dmesg.txt, log.tar.gz which contains /var/log and ifconfig.txt which contains the ifconfig output.

Following the first successful user login then the nics are listed in the following order whilst shutting down:
Eth0 – 3com
Eth1 – HP onboard device
Eth2 – realtek

Following a full reboot the nics are now ordered in yast2:
Eth0 – 3com
Eth1 – HP onboard device
Eth2 – realtek

Delete middle ethernet device (which was reported as HP) and it then reappeared as Realtek. HP device has moved down the list.

Use yast to configure correctly – static IP, mask, default gateway[remembered this], DNS[had lost this]. Still no ethernet access.
Shutdown & restart.

Networking works ok this time. 
Captured dmesg_working.txt and ifconfig_working.txt files.

Comment 1 tim chappell 2007-09-03 13:02:03 UTC

Created attachment 161490 [details]
dmesg.txt

dmesg at failure point.

Comment 2 tim chappell 2007-09-03 13:03:00 UTC

Created attachment 161491 [details]
ifconfig failing report

Comment 3 tim chappell 2007-09-03 13:04:03 UTC

Created attachment 161494 [details]
/var/log files at failing point

Comment 4 tim chappell 2007-09-03 13:04:41 UTC

Created attachment 161495 [details]
lspci output

Comment 5 tim chappell 2007-09-03 13:05:15 UTC

Created attachment 161496 [details]
dmesg of working boot

Comment 6 tim chappell 2007-09-03 13:05:41 UTC

Created attachment 161497 [details]
ifconfig working report

Comment 7 Michal Zugec 2007-09-04 16:53:15 UTC

duplicate report, already fixed for Beta3

2007-09-03 12:08:17 <3> linux(3542) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: cannot stat `/var/lib/dhcpcd/dhcpcd-*.cache': No such file or directory
2007-09-03 12:08:17 <3> linux(3542) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: cannot stat `/etc/udev/rules.d/70-net_persistent_names.rules': No such file or directory

it should be /etc/udev/rules.d/70-persistent-net.rules file copied into installed system

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

Comment 8 tim chappell 2007-09-06 08:35:51 UTC

Retested with 10.3 beta3 and same issue remains - ie this is not necessarily a duplicate of 292375.

I'm attaching another tar.gz which includes all the relevant info just after install/reboot, following reconfiguration with yast2 (at which point it doesn't work) and then following a further reboot at which point the interface works correctly. Includes yast2 snapshots showing misnamed interfaces.

Comment 9 tim chappell 2007-09-06 08:38:19 UTC

Created attachment 162229 [details]
tar.gz containing /var/log, dmesg and ifconfig at various points.

Comment 10 tim chappell 2007-09-06 08:39:39 UTC

Retested with 10.3 beta3 and same issue remains - ie this is not necessarily a
duplicate of 292375 (not sure whether that is resolved or not).

I'm attaching another tar.gz which includes all the relevant info just after
install/reboot, following reconfiguration with yast2 (at which point it doesn't
work) and then following a further reboot at which point the interface works
correctly. Includes yast2 snapshots showing misnamed interfaces.

Comment 11 Michal Zugec 2007-09-06 14:42:02 UTC

Oh no:
2007-09-06 08:59:09 <3> linux(3537) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: missing destination file operand after `/etc/udev/rules.d/70-persistent-net.rules/mnt/etc/udev/rules.d'

missing space between source and destination ;-(
The only problem is that udev is not copy between reboot. That's why network devices names are changed. We have NAME option in ifcfg-eth* files to show interface name.

yast2-network-2.15.74

Comment 12 Katarina Machalkova 2007-09-13 09:14:50 UTC

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

Comment 13 tim chappell 2007-09-21 09:01:20 UTC

Verified as working correctly in RC1. Thanks!