[Bug 901565] New: YaST forgets bridged devices when not visiting "Bridged Devices" tab
http://bugzilla.opensuse.org/show_bug.cgi?id=901565 Bug ID: 901565 Summary: YaST forgets bridged devices when not visiting "Bridged Devices" tab Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: leen.meyer@ziggo.nl QA Contact: jsrain@suse.com Found By: --- Blocker: --- When editing the network settings of a bridge, YaST forgets the bridged devices if one does not visit the "Bridged Devices" tab. A bridge without devices means no working network (via that bridge). This happens in a fresh install of 13.2-RC1 in a virtual machine: virt-install --connect qemu:///system --graphics=vnc --name=os-13-2.site --os-type=linux --os-variant=opensuse12 --ram=2048 --vcpus=1 --network=bridge=br0,mac=02:00:0A:00:0D:02 --disk=path=/var/lib/libvirt/images/os-13-2.site.img,size=10 --cdrom=/var/lib/libvirt/images/openSUSE-13.2-DVD-Build0019-x86_64.iso Precondition: a bridge (br0) with an attached device (eth0) Reproducable: always (minimal text-mode and graphical with KDE) Expected behavior: YaST remembers the bridged devices and sets up the bridge as it was before running yast lan. Next instructions are for text-mode (konsole or non-graphical). brctl show br0 --> 1 device listed (eth0) yast lan --> edit bridge br0 --> do NOT visit the "Bridged Devices" tab, but just press "Next", press "OK". brctl show br0 --> No devices! yast lan -> edit bridge br0 --> visit the "Bridged Devices" tab, checkmark eth0, press "Next", press "OK". brctl show br0 --> 1 device listed: eth0 yast lan --> edit bridge br0 --> visit the "Bridged Devices" tab, note that eth0 is checkmarked, press "Next", press "OK". brctl show br0 --> 1 device listed: eth0 Kind regards, Leendert Meyer -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=901565 Leendert Meyer <leen.meyer@ziggo.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leen.meyer@ziggo.nl -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=901565 http://bugzilla.opensuse.org/show_bug.cgi?id=901565#c3 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |YaST2 Version|13.2 RC 1 |Current Product|openSUSE Distribution |openSUSE Tumbleweed Flags|needinfo?(leen.meyer@ziggo. | |nl) | --- Comment #3 from Tomáš Chvátal <tchvatal@suse.com> --- Does not look like the code was changed. Logs are provided by the user, moving to TW target. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=901565 http://bugzilla.opensuse.org/show_bug.cgi?id=901565#c4 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Michal Filka <mfilka@suse.com> --- There were several updates regarding bridge slaves handling in yast2-network in past months. I'm not able to reproduce the issue with latest yast2-network in SLE-12-SP3 / master / TW -> closing as fixed. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com