Bug 395014 - Network not configured during automatic configuration
Summary: Network not configured during automatic configuration
Status: RESOLVED FIXED
: 395079 (view as bug list)
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 3plus
Hardware: Other Other
: P5 - None : Blocker (vote)
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-28 11:12 UTC by Holger Sickenberg
Modified: 2021-02-26 20:13 UTC (History)
3 users (show)

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
coolo: SHIP_STOPPER+

Attachments
hwinfo.txt (515.65 KB, text/plain)
2008-05-28 11:12 UTC, Holger Sickenberg 		Details
/y2logs.tgz (348.50 KB, application/x-gzip)
2008-05-28 11:13 UTC, Holger Sickenberg 		Details
output.txt (3.70 KB, text/plain)
2008-05-30 10:11 UTC, Holger Sickenberg 		Details
logs.tgz (407.38 KB, application/x-compressed-tar)
2008-05-30 14:30 UTC, Holger Sickenberg 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Sickenberg 2008-05-28 11:12:27 UTC 
I installed Build 130 i386 Gnome with automatic configuration.

But when installation was finished, no network device was configured:

fornax:/tmp # l /etc/sysconfig/network/
total 80
drwxr-xr-x 6 root root  4096 May 28 03:20 ./
drwxr-xr-x 7 root root  4096 May 28 12:10 ../
-rw-r--r-- 1 root root  8623 May 28 03:00 config
-rw-r--r-- 1 root root  6863 May 28 12:20 dhcp
drwxr-xr-x 2 root root  4096 May 28 03:08 if-down.d/
drwxr-xr-x 2 root root  4096 May 28 03:09 if-up.d/
-rw-r--r-- 1 root root   174 May 23 14:23 ifcfg-lo
-rw-r--r-- 1 root root 27766 May 23 14:23 ifcfg.template
-rw-r--r-- 1 root root   239 May 23 14:23 ifroute-lo
drwx------ 2 root root  4096 May 22 04:36 providers/
drwxr-xr-x 2 root root  4096 May 28 03:20 scripts/
Comment 1 Holger Sickenberg 2008-05-28 11:12:52 UTC 
Created attachment 218558 [details]
hwinfo.txt
Comment 2 Holger Sickenberg 2008-05-28 11:13:08 UTC 
Created attachment 218559 [details]
/y2logs.tgz
Comment 3 Stephan Kulow 2008-05-29 05:43:47 UTC 
this sounds like a duplicate of 395079 - for me network setup worked just fine.
Comment 4 Michal Zugec 2008-05-29 15:34:11 UTC 
Hm, here the problem is that output from yast2-hardware reports link status nil, but directly from hwinfo the status is true. And YaST configures first "connected" device (in case no NM is used)
Martin?
Comment 5 Michal Zugec 2008-05-29 16:12:06 UTC 
Can you provide output from :
echo '`Read(.probe.netcard)'|/usr/lib/YaST2/bin/y2base stdio scr
Comment 6 Holger Sickenberg 2008-05-30 10:11:49 UTC 
Created attachment 219089 [details]
output.txt
Comment 7 Holger Sickenberg 2008-05-30 14:30:48 UTC 
Created attachment 219181 [details]
logs.tgz
Comment 8 Michal Zugec 2008-05-30 14:35:36 UTC 
eth1 didn't propagate carrier status because link was down (as a workaround - "ip link set eth1 up")
Comment 9 Stephan Kulow 2008-06-02 05:31:28 UTC 
*** Bug 396135 has been marked as a duplicate of this bug. ***
Comment 10 Stephan Kulow 2008-06-02 05:33:03 UTC 
Hmm, I just marked #396135 as duplicate, but there the problem is that only eth1 is configured and eth0 is not. Maybe not the same problem?
Comment 11 Michal Zugec 2008-06-02 07:30:53 UTC 
fixed in yast2-network-2.16.47
problem description:
- before network configuration proposal there is hardware detection
- in hardware detection there should modprobe drivers for all network devices when needed and also set link status to up
- here is the problem - for "setting link status" there was hardcoded "eth0"
Comment 12 Michal Zugec 2008-06-02 07:36:36 UTC 
*** Bug 395079 has been marked as a duplicate of this bug. ***