[Bug 857340] New: needed 3 runs of "yast2 lan" to configure a bridge
https://bugzilla.novell.com/show_bug.cgi?id=857340
https://bugzilla.novell.com/show_bug.cgi?id=857340#c0
Summary: needed 3 runs of "yast2 lan" to configure a bridge
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
AssignedTo: mfilka@suse.com
ReportedBy: jdsn@suse.com
QAContact: jsrain@suse.com
CC: mvidner@suse.com
Found By: Development
Blocker: ---
I installed an openSUSE 13.1 (no update) on my workstation and installed all
updates (available on 2014-01-03) right after (not during) the installation
(before the first login).
In the installation phase I kept the default network configuration (ifup with
dhcp).
In the installed system I wanted to add a bridge device and have the only NIC
configured as bridged device. Here is what happened:
- ran yast2 lan first time
+ deleted configuration for "em1"
+ added bridge "br0"
+ wanted to add the "em1" device to the bridge, but NO device was available
+ so I saved the config as it was at that moment (bridge without bridged
device)
and exited
- verified current config:
# grep BRIDGE_PORTS /etc/sysconfig/network/ifcfg-br0
BRIDGE_PORTS=''
- ran yast2 lan second time
+ edit bridge "br0"
+ add "em1" as bridged device (now the device was available)
+ saved the configuration and exited
- verified the change:
# grep BRIDGE_PORTS /etc/sysconfig/network/ifcfg-br0
BRIDGE_PORTS='em1'
- surprisingly the bridge had no bridged device "em1":
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000000000000 no
- furthermore, there no longer was a device called "em1":
# ip a
1: lo:
https://bugzilla.novell.com/show_bug.cgi?id=857340
https://bugzilla.novell.com/show_bug.cgi?id=857340#c1
--- Comment #1 from J. Daniel Schmidt
https://bugzilla.novell.com/show_bug.cgi?id=857340
https://bugzilla.novell.com/show_bug.cgi?id=857340#c2
--- Comment #2 from J. Daniel Schmidt
participants (1)
-
bugzilla_noreply@novell.com