Bug 820408

Summary: network interfaces show as "not configured" although they clearly are
Product: [openSUSE] openSUSE Tumbleweed Reporter: Per Jessen <per>
Component: YaST2Assignee: Michal Filka <mfilka>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: 13.1 Milestone 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screenshot of yast network interface config
y2logs as saved by save_y2logs

Description Per Jessen 2013-05-17 11:17:34 UTC
Created attachment 539808 [details]
screenshot of yast network interface config

User-Agent:       Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0

Hardware:  taggart2, 1U zattoo-box, quad core, 2Gb RAM, dual NICs.
Software   openSUSE 13.1 M1
Process:   network install over pxe+ssh, root on iSCSI.


# l /etc/sysconfig/network/
total 100
drwxr-xr-x 6 root root  4096 May 17 13:13 ./
drwxr-xr-x 5 root root  4096 May 17 12:41 ../
-rw-r--r-- 1 root root 12911 May 17 12:50 config
-rw-r--r-- 1 root root 10592 May 17 12:50 dhcp
-rw-r--r-- 1 root root   193 May 17 12:50 ifcfg-enp13s0
-rw-r--r-- 1 root root    80 May 17 12:40 ifcfg-enp14s0
-rw------- 1 root root   151 Mar  6 02:57 ifcfg-lo
-rw-r--r-- 1 root root 29387 Mar  6 02:57 ifcfg.template
drwxr-xr-x 2 root root  4096 May 17 12:38 if-down.d/
-rw-r--r-- 1 root root   239 Mar  6 02:57 ifroute-lo
drwxr-xr-x 2 root root  4096 May 17 12:39 if-up.d/
drwx------ 2 root root  4096 Feb  3 08:16 providers/
drwxr-xr-x 2 root root  4096 May 17 12:39 scripts/

Although 'enp13s0' and 'enp14s0' are both configured, yast doesn't seem to think so, see screenshot attached.  

Reproducible: Always
Comment 1 Per Jessen 2013-05-17 11:19:45 UTC
Created attachment 539810 [details]
y2logs as saved by save_y2logs
Comment 2 Michal Filka 2013-05-21 08:29:05 UTC
yast is unable to handle "renamed" interfaces. Its implementation of handling configuration which is named otherwise than ifcg-eth* is full of bugs. It is on my private TODO list right on second place ... just after fixing high prio bugs. 

However, it has to be fixed by the 13.1 release.
Comment 3 Michal Filka 2014-02-12 14:44:42 UTC
Many fixes have been provided starting in yast2 v2.24.5. Handling new device names works in 13.1