Bug 398745 - network interface down during second stage
Summary: network interface down during second stage
Status: RESOLVED DUPLICATE of bug 399645
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 3
Hardware: PowerPC Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-10 07:40 UTC by Olaf Hering
Modified: 2008-07-16 15:39 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
bug398745.tar.bz2 (293.37 KB, application/x-bzip)
2008-06-10 07:50 UTC, Olaf Hering
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Hering 2008-06-10 07:40:08 UTC
11.0rc3 from iso image via nfs

cmdline for installation was:
 append="start_shell quiet sysrq=1 nosshkey install=nfs://10.10.0.100/dist/install/openSUSE-11.0-RC3/openSUSE-11.0-RC3-DVD-ppc.iso "

I reused an existing lvm partition, did a default gnome install with german locale.
In second stage, the network was up but no default route was set.

There was a popup 'Herunterladen / Frische Repository auf openSUSE-DVD-11-0:' during  'Konfiguration wird abgeschlossen'. At this point, the installation stopped due to incomplete network configration.
Comment 1 Olaf Hering 2008-06-10 07:40:59 UTC
an 'ifdown eth0 ; ifup eth0' in an xterm fixed the network.
Comment 2 Olaf Hering 2008-06-10 07:50:11 UTC
Created attachment 221170 [details]
bug398745.tar.bz2
Comment 3 Michal Zugec 2008-06-10 07:51:31 UTC
Please use english for describing popups messages.
What contains /etc/install.inf (or /var/lib/YaST2/install.inf) ?
Comment 4 Olaf Hering 2008-06-10 08:43:16 UTC
its all attached.

I see calls to listen_remote_ipp, it _could_ be that the route -n is broken at that point. But I cant say for sure what the automatic network configration is doing, maybe the network setup is already broken once the listen_remote_ipp runs. The network is running ok once yast starts.
Comment 5 Michal Zugec 2008-06-10 09:17:43 UTC
From install.inf:
NetConfig: dhcp

from y2log :
2008-06-05 13:30:45 <1> cherimoya(2828) [YCP] clients/save_network.ycp:256 Network Configuration:
BOOTPROTO='dhcp'
STARTMODE='onboot'
NAME='NetXtreme BCM5704S Gigabit Ethernet'

From yast part is everything ok. How is network started at second stage? Compare with attachement https://bugzilla.novell.com/attachment.cgi?id=220748 
Comment 6 Olaf Hering 2008-06-10 09:22:15 UTC
I'm not sure what you mean.

The network is started via dhcp. The network is running ok for most part of second stage. Just at the end of it, after network config and before yast tries to access the install iso on nfs, the default route is gone.
Its not specific to gnome, happens also with a default kde 3.5 install.

Maybe yast does not do a ifdown eth0; ifup eth0, but something else?

I also does not happen on i386 with this command line:

linemode=1 install=nfs://dist.suse.de/dist/install/openSUSE-11.0-RC3/openSUSE-11.0-RC3-DVD-i386.iso panic=9 sysrq=1 start_shell usessh=1 sshpassword=foobar vnc=1 vncpassword=12345678 nosshkey quiet linuxrcstderr=/dev/console netdevice=00:09:6b:b5:0c:5d

I will try a vnc installation now.
Comment 7 Michal Zugec 2008-06-10 10:04:29 UTC
but anyway there is problem while mounts nfs inst.source (and you don't need default route for that)
can you try manually mount inst.source and attach output?
Comment 8 Olaf Hering 2008-06-10 10:37:45 UTC
I was unable to mount dist, unless I do ifdown/ifup
Comment 9 Olaf Hering 2008-06-10 12:03:31 UTC
the interface is down, thats why nothing works.
It does not happen with a vnc install.
Comment 10 Michal Zugec 2008-06-10 12:48:17 UTC
reproduced
workaround : "ip link set eth0 up"
Comment 11 Michal Zugec 2008-06-10 12:52:57 UTC
eeh, sorry - this workaround doesn't work
Comment 12 Joshua Grant 2008-06-10 16:33:25 UTC
I am still seeing this issue with RC4.
Comment 13 Michal Zugec 2008-06-13 06:30:03 UTC

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