Bug 293366

Summary:	Network devices do change their order
Product:	[openSUSE] openSUSE 10.3	Reporter:	Holger Sickenberg <holgi>
Component:	Installation	Assignee:	Katarina Machalkova <kmachalkova>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	aschnell, jdsn
Version:	Beta 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs.tgz

Description Holger Sickenberg 2007-07-20 08:40:44 UTC

I configured one of the two network cards during installation. In running system network did not run and I could not start it either.

Reason was that the card which was eth1 during installation is eth0 now. So renaming /etc/sysconfig/network/ifcfg-eth1 in ifcfg-eth0 solved the problem.

But we need a solution here where "device names" do stay the same.

Comment 1 Christian Zoz 2007-07-20 11:51:10 UTC

This may be a duplicate of bug 292375.

Please check if interface names change between stage 1 and 2 of installation, or if the change between stage 2 and the next booting.

Comment 2 Christian Zoz 2007-08-31 09:56:48 UTC

Holger, i guess this ia really duplicate. Please reopen if i'm wrong.

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

Comment 3 Holger Sickenberg 2007-09-06 12:21:12 UTC

same problem again with Beta 3.

Timestamp looks like 70-persistent-net.rules was just written in stage 2

Comment 4 Holger Sickenberg 2007-09-06 12:21:57 UTC

Created attachment 162348 [details]
y2logs.tgz

Comment 5 Holger Sickenberg 2007-09-06 12:22:36 UTC

-> so reopening.

Comment 6 Christopher Stender 2007-09-11 15:06:13 UTC

From the y2log-1:

2007-09-06 13:56:10 <3> 10.10.4.37(3723) [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'
2007-09-06 13:56:10 <3> 10.10.4.37(3723) [bash] ShellCommand.cc(shellcommand):78 Try `/bin/cp --help' for more information.

Thats the reason why there is no /etc/udev/rules.d/70-persistent-net.rules at the beginning of state2. Of course interface names can change then.

Reassigning to yast2-maintainers.

Comment 7 Christian Zoz 2007-09-11 19:22:47 UTC

I guess the following is clear but i like to make it sure:

Please also check that the new generated file will _not_ be copied into installed system in case of update. Better, don't copy (or create) the file if /mnt/etc/udev/rules.d/70-persistent-net.rules already exists.

We have to test this all again before RC1!!!

Comment 8 Christian Zoz 2007-09-12 09:14:12 UTC

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

Comment 9 Katarina Machalkova 2007-09-12 12:04:09 UTC

- Do not rewrite udev rules file during update (if it already exists 
  in Installation::destdir) (#293366c#7)

Fixed yast2-network 2.15.76

Btw, the issue with missing space in '/bin/cp -p /etc/udev/rules.d/70-persistent-net.rules/mnt/etc/udev/rules.d' has been already fixed with bug #307162

Comment 10 Christian Zoz 2007-09-13 09:34:52 UTC

So an installation from STABLE should work now?

Holger, can you confirm that this works now, or should we try again?