711713 – yast2 NFS port opening dialog with unnamed network interface

Bug 711713 - yast2 NFS port opening dialog with unnamed network interface

Summary: yast2 NFS port opening dialog with unnamed network interface

Status:	RESOLVED DUPLICATE of bug 677251

Alias:	None

Product:	openSUSE 11.4
Classification:	openSUSE
Component:	YaST2 (show other bugs)
Version:	Final
Hardware:	x86-64 openSUSE 11.4

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Martin Vidner
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2011-08-11 08:55 UTC by melchiaros melchiaros
Modified:	2012-01-31 16:19 UTC (History)
CC List:	0 users

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

Attachments
yast2,messages,warn (3.52 MB, application/x-gzip) 2011-08-11 08:55 UTC, melchiaros melchiaros	Details
the screenshot - first line (142.30 KB, image/jpeg) 2011-08-11 08:58 UTC, melchiaros melchiaros	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 melchiaros melchiaros 2011-08-11 08:55:51 UTC

Created attachment 445329 [details]
yast2,messages,warn

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

When I choose the Firewall port opening dialog in the first line is an checked unnamed network interface. -> see screenshot.

Accepting it causes an message like: Could not open "" network interface.

I´ve seen that also some days ago in openSUSE 12.1 MS3.

yast2 logs will be added.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 melchiaros melchiaros 2011-08-11 08:57:17 UTC

Get it with:
yast2 -> NFS-Server-> Open Firewall-Port

Comment 2 melchiaros melchiaros 2011-08-11 08:58:17 UTC

Created attachment 445330 [details]
the screenshot - first line

Comment 3 melchiaros melchiaros 2011-08-11 08:59:22 UTC

File list:

rpm -qa | grep nfs
yast2-nfs-common-2.18.1-8.1.noarch
limal-nfs-server-perl-debuginfo-1.6.1-9.1.x86_64
nfs-kernel-server-1.2.3-27.1.x86_64
limal-nfs-server-1.6.1-9.1.x86_64
nfsidmap-0.23-13.1.x86_64
limal-nfs-server-debuginfo-1.6.1-9.1.x86_64
yast2-nfs-client-2.19.3-4.1.noarch
nfs-client-1.2.3-27.1.x86_64
limal-nfs-server-perl-1.6.1-9.1.x86_64
nfsidmap-debugsource-0.23-13.1.x86_64
nfsidmap-debuginfo-0.23-13.1.x86_64
yast2-nfs-server-2.18.1-8.1.noarch
limal-nfs-server-debugsource-1.6.1-9.1.x86_64
nfs-client-debuginfo-1.2.3-27.1.x86_64


On Kernel:

kernel-desktop-3.0.0-8.1.x86_64

Comment 4 Martin Vidner 2012-01-31 16:19:04 UTC

It is because of "/etc/sysconfig/network/ifcfg-"

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