[Bug 820407] New: Unusual network config - enp13s0 and enp14s0, but one is called eth1
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c0
Summary: Unusual network config - enp13s0 and enp14s0, but one
is called eth1
Classification: openSUSE
Product: openSUSE Factory
Version: 13.1 Milestone 1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: per@computer.org
QAContact: qa-bugs@suse.de
Found By: ---
Blocker: ---
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.
# ip addr
2: enp13s0:
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c
FeiXiang Zhang
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c1
--- Comment #1 from Per Jessen
Where did that 'eth1' come from??
'eth1' is the interface for the iscsi root device.
Also, for some reason both interfaces are configured with BOOTPROTO='dhcp' and STARTMODE='nfsroot', although I only configured one during installation.
Probably related to bug#820408 y2logs are in attachment#539810 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c2
--- Comment #2 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c3
Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c4
--- Comment #4 from Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c5
--- Comment #5 from Per Jessen
I would make a guess that there is no entry in /etc/udev/rules.d/70-persistent-net.rules that matches the MAC address of eth1 (00:30:48:90:80:77). Well, that would be for 12.3.
This was a fresh Factory install, Milestone 1. There should not have been a "70-persistent-net.rules", I think.
Device renaming requires that the device not be in the UP state. So, if you have root on iSCSI, then any interface renaming on the supposedly-pinned interface needs to occur before iSCSI starts, i.e. in the initrd. I suppose the udev renaming rule files are not present in the initrd.
Okay, interesting. See also recently opened report, bug#842450. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c6
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c7
Per Jessen
Can you check if "70-persistent-net.rules" is empty?
The system was 13.1M1, it's long gone, but I'm pretty certain there was no "70-persistent-net.rules". With 13.1B1 there isn't one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c8
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c9
--- Comment #9 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c10
--- Comment #10 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c11
Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c12
--- Comment #12 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c13
--- Comment #13 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c14
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c15
Per Jessen
This usually happen when we already have the name set to eth1 in out case and ifup already as ran for eth1, meaning that ifup eth1 happen and only before we are trying to rename, ending up in that error.
This could be an issue with 77-network.rules.
I would suggest to rename /usr/lib/udev/rules.d/77-network.rules to /usr/lib/udev/rules.d/86-network.rules, reboot and try again udevadm test ... or check if eth1 has been renamed.
Okay, I tried that - eth1 was not renamed, and the udevadm test was identical to the previous one.
Or rename /usr/lib/udev/rules.d/80-net-name-slot.rules to /usr/lib/udev/rules.d/76-net-name-slot.rules and of course reboot and check if the network has been renamed.
Okay, I tried that - eth1 was not renamed. udevadm test was also identical. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c16
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c17
--- Comment #17 from Marius Tomaschewski
I would suggest to rename /usr/lib/udev/rules.d/77-network.rules to /usr/lib/udev/rules.d/86-network.rules,
sysconfig installs a 77-network.rules since ages (9.x?), that is when the 80-net-name-slot.rules renames, it is already too late. I'd prefer to not rename 77-network.rules as it is mentioned in diverse docs ... (In reply to comment #14)
Or rename /usr/lib/udev/rules.d/80-net-name-slot.rules to /usr/lib/udev/rules.d/76-net-name-slot.rules and of course reboot and check if the network has been renamed.
Yes, better. Don't forget to call "mkinitrd" to update the rules in the initrd (does mkinitrd [dracul?] copy the rules to the initrd?). On iSCSI-root the rename is possible only in the initrd. The system cannot change it any more. So "udevadm test" will show it, but to test if the rename realy works, a reboot is required. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c18
Per Jessen
Hmm ok, will try to look into it, but still not possibility of reproduce the issue.
Can you please tell me what machine/network adapters are you using?
It is a Supermicro PDSML-LN2+ board, it has two onboard GigE interfaces, one Intel 82573E, one Intel 82573L. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c19
--- Comment #19 from Per Jessen
(In reply to comment #14)
Or rename /usr/lib/udev/rules.d/80-net-name-slot.rules to /usr/lib/udev/rules.d/76-net-name-slot.rules and of course reboot and check if the network has been renamed.
Yes, better.
Don't forget to call "mkinitrd" to update the rules in the initrd (does mkinitrd [dracul?] copy the rules to the initrd?).
Okay, that broke the system :-) although it boots from the iscsi drive, it cannot complete the boot-up due to not getting access to the root filesystem. I'll have to get a serial console on this to see what's happening. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c
Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c20
--- Comment #20 from Per Jessen
(In reply to comment #17)
(In reply to comment #14)
Or rename /usr/lib/udev/rules.d/80-net-name-slot.rules to /usr/lib/udev/rules.d/76-net-name-slot.rules and of course reboot and check if the network has been renamed.
Yes, better.
Don't forget to call "mkinitrd" to update the rules in the initrd (does mkinitrd [dracul?] copy the rules to the initrd?).
Okay, that broke the system :-) although it boots from the iscsi drive, it cannot complete the boot-up due to not getting access to the root filesystem. I'll have to get a serial console on this to see what's happening.
Well, the problem seems to be that the faulty network config (see bug#843451) was copied into the initrd, which causes the startup to run dhcp to get an address for eth0/enp14s0. This times out, but there is no attempt to try dhcp with eth1/enp13s0. I'll try to fix the initrd with a working network config. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c21
--- Comment #21 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c22
--- Comment #22 from Per Jessen
(In reply to comment #14)
Or rename /usr/lib/udev/rules.d/80-net-name-slot.rules to /usr/lib/udev/rules.d/76-net-name-slot.rules and of course reboot and check if the network has been renamed.
Yes, better.
Don't forget to call "mkinitrd" to update the rules in the initrd (does mkinitrd [dracul?] copy the rules to the initrd?).
I have just unpacked the latest initrd, there is no "*-net-name-slot.rules" file. taggart7:/tmp/gg # find . -name \*rules /etc/udev/rules.d/70-persistent-net.rules /usr/lib/udev/rules.d/10-dm.rules /usr/lib/udev/rules.d/60-persistent-storage.rules /usr/lib/udev/rules.d/50-udev-default.rules /usr/lib/udev/rules.d/77-network.rules /usr/lib/udev/rules.d/13-dm-disk.rules /usr/lib/udev/rules.d/50-firmware.rules /usr/lib/udev/rules.d/60-persistent-input.rules /usr/lib/udev/rules.d/61-msft.rules /usr/lib/udev/rules.d/95-dm-notify.rules /usr/lib/udev/rules.d/80-drivers.rules -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c23
--- Comment #23 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c24
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c25
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c26
--- Comment #26 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c27
--- Comment #27 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c28
--- Comment #28 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c29
Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c30
--- Comment #30 from Per Jessen
Created an attachment (id=561133) --> (http://bugzilla.novell.com/attachment.cgi?id=561133) [details] 60-persistent-input.rules from the initrd
Ooopss, I guess I need another coffee, obviously a bit too early. Hmm, there is no "/etc/udev/rules.d/70-persistent-net.rules" in the initrd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c31
--- Comment #31 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c32
--- Comment #32 from Per Jessen
I don't honestly understand how you can have eth1 (or maybe I do) ?!
What's so special about eth1? I don't understand your confusion. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c33
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c34
--- Comment #34 from Per Jessen
You shouldn't have it, it should be something like enp14s0.
Haha, yeah, that's what the report is all about :-) As far as I've understood, the problem is that systemd should be renaming both eth0 and eth1 appropriately, but as this doesn't happen in the initrd, only the unused one (eth0) is renamed (later).
Can you boot the installer in text mode and switch to the console where you can see what network adapters you have (ifconfig -a)?
I'm not sure if in graphical mode you can switch to the console.
I'm always in text-mode anyway, no probs. It'll have to wait until tomorrow, I think. (which time-zone are you on?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c35
Per Jessen
You shouldn't have it, it should be something like enp14s0. Can you boot the installer in text mode and switch to the console where you can see what network adapters you have (ifconfig -a)?
I'm not sure if in graphical mode you can switch to the console.
You can (Ctrl-Alt-Fx), but this is the output of "ifconfig -a" : enp13s0 Link encap:Ethernet HWaddr 00:30:48:92:F3:14 inet6 addr: fe80::230:48ff:fe92:f314/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:256 (256.0 b) TX bytes:2064 (2.0 Kb) Interrupt:11 Memory:ee100000-ee120000 enp14s0 Link encap:Ethernet HWaddr 00:30:48:92:F3:15 inet addr:10.42.8.54 Bcast:10.42.15.255 Mask:255.255.248.0 inet6 addr: fe80::230:48ff:fe92:f315/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:76478 errors:0 dropped:0 overruns:0 frame:0 TX packets:6890 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:115771273 (110.4 Mb) TX bytes:492899 (481.3 Kb) Interrupt:10 Memory:ee200000-ee220000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth1 was correctly renamed because the network isn't in use at this point. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c36
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c37
Per Jessen
Now that is strange. You have the network setup correctly, but for whatever reason after the installation enp14s0 ends-up eth1.
Um, that's not really so strange. The installation system is booted over PXE, there is no iSCSI involved at this point. The kernel and the initrd are transferred, then booted - no network active. The driver enumerates the interface first as eth0 and eth1, and they're then appropriately renamed by systemd/udev/whoever. Once the system is installed, it boots over PXE+iSCSI, i.e. first we connect the iSCSI drive as drive 0x80, then the system is booted from that. Because eth1 is now active, it cannot be renamed.
I will try to reproduce this, is there a specific way you boot and/or setup your machine?
PXE+tftp+ipxe+iscsi -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c38
--- Comment #38 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c39
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c40
--- Comment #40 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c41
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c42
--- Comment #42 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c43
Lee Duncan
Lee, can you please take a look at the problem, looks to me like iscsi issue.
Robert: not clear what you are asking. You supplied a patch to initrd udev setup script. Does that fix the problem? I have not been able to reproduce this bug, so I cannot test the patch at this time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c44
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c45
--- Comment #45 from Per Jessen
Per, please test the provided mkinitrd package. I cant test it myself because interfaces are not renamed in hyperv guests, and due to bnc#846193.
Okay - on my system "taggart7", I updated mkinitrd to 2.8 and applied Robert's patch from comment#40, and rebuilt the initrd. The network feature and my e1000e module were not included by default, making the system non bootable. 2nd try - I ran mkinitrd with "-m e1000e -f network", but the system still didn't boot. The network interfaces were renamed, but not brought up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c46
--- Comment #46 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c47
Per Jessen
The patch only suppose to help the running system, but if this happens (setup of the network) before udev has the opportunity to rename the network, then must be in PXE initrd or something like that. I really don't know.
Well, the renaming seems to work, but the interfaces aren't brought up. This worked previously, so I don't understand why it has changed now. Is it possible that the necessary network interface isn't being started due to having been renamed (to enpxxxxx) ? It worked when it was called "eth1". There is no earlier initrd. The system first boots PXE, which chainloads iPXE which in turn hooks up the iSCSI disk and lets the system boot from that. The initrd is loaded from the root filesystem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c48
--- Comment #48 from Olaf Hering
(In reply to comment #46)
The patch only suppose to help the running system, but if this happens (setup of the network) before udev has the opportunity to rename the network, then must be in PXE initrd or something like that. I really don't know.
Well, the renaming seems to work, but the interfaces aren't brought up. This worked previously, so I don't understand why it has changed now. Is it possible that the necessary network interface isn't being started due to having been renamed (to enpxxxxx) ? It worked when it was called "eth1".
Bringing up the network is not straight forward if the initrd was built on a system with different network settings, like building it on the nfsroot server. Try to boot with 'interface=eth0 dhcp_macaddresses=eth0' (change eth0 to the actual interface name). If that works, rerun mkinitrd in that state and see if this state gets included into the initrd. I think it should. If there is still an issue what -f network -m e1000 is required, please open a new bug if there isnt one already. Appearently the mkinitrd part of iscsi is not working properly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c49
--- Comment #49 from Per Jessen
Bringing up the network is not straight forward if the initrd was built on a system with different network settings, like building it on the nfsroot server.
Yes, I understand that, but here I built it on the same system. I kept the working initrd as a backup so I would still have a working system if the new initrd was bad :-)
Try to boot with 'interface=eth0 dhcp_macaddresses=eth0' (change eth0 to the actual interface name). If that works, rerun mkinitrd in that state and see if this state gets included into the initrd. I think it should.
Hmm, I see - because the working system uses eth1, the initrd would be built to use that too? I tried booting with just "interface=enp14s0", but that made no difference. Then I tried "interface=enp14s0 dhcp_macaddresses=enp14s0", which worked! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c50
--- Comment #50 from Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c51
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c52
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c53
Per Jessen
https://bugzilla.novell.com/show_bug.cgi?id=820407
https://bugzilla.novell.com/show_bug.cgi?id=820407#c54
--- Comment #54 from Bernhard Wiedemann
http://bugzilla.novell.com/show_bug.cgi?id=820407
http://bugzilla.novell.com/show_bug.cgi?id=820407#c55
Robert Milasan
participants (1)
-
bugzilla_noreply@novell.com