|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST Network - bridge br0 config not read properly | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Oldrich Horak <horacius> |
| Component: | YaST2 | Assignee: | Michal Filka <mfilka> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aspiers, forgotten_O04XDU3xXI, forgotten_QtBI7gWTIh, mpluskal, thardeck, wagner-thomas, wspitz |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | NetworkInterfaces.patch | ||
|
Description
Oldrich Horak
2013-11-22 08:49:41 UTC
To the reporter: The steps to reproduce above contain "openSUSE 12.3" while the product attribute is set to "openSUSE 13.1". Which one is correct? Michal, JFYI: the bridge is created by "lan_proposal" client: https://github.com/yast/yast-vm/blob/master/src/modules/VM_XEN.rb#L378 Sorry for the mistake, the right version is "openSUSE 13.1" in the first step. I experience the same problem with the KVM hypervisor in openSUSE 13.1 (in the initial bug-report XEN was used). With some more details: * If the bridge is set up with Yast->Install Hypervisor, then I experience the same problems as in the original bugreport. * If I edit some network related stuff with the Virtual Machine Manager, my previously DHCP-configured devices are set to static without any given IP (visible in Yast->Network). The machine will get itself a 169.xx.xx.xx address. * If the bride is set up with Yast->Install Hypervisor the bride is later visible with "ifconfig" and "brctl". * If the bridge is deleted and set up again with the Virtual Machine Manager, it is not visible with "ifconfig" nor with "brctl"; but it's visible with Yast->Network The problem is an error in /usr/share/YaST2/modules/NetworkInterfaces.rb. In case of a bridge, the function GetEthTypeFromSysfs returns the type "bridge", but calling functions expect a "br" device type. Following patch should solve the problem. Created attachment 571072 [details]
NetworkInterfaces.patch
*** Bug 853998 has been marked as a duplicate of this bug. *** @Waldemar: Thanks for the patch. Its way into main github tree can be tracked here https://github.com/yast/yast-yast2/pull/161 *** Bug 846813 has been marked as a duplicate of this bug. *** The suggested fix does also work for me, thanks. Fixed version was pushed into OBS. Fix is present in yast2.rpm v3.0.11 Thanks all for help This is an autogenerated message for OBS integration: This bug (851769) was mentioned in https://build.opensuse.org/request/show/210655 13.1 / yast2 openSUSE-RU-2013:1902-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 851769 CVE References: Sources used: openSUSE 13.1 (src): yast2-3.0.11-7.1 I suspect that this fix might not sufficient. Does it assume that all bridge devices begin with "br"? If so, please reopen, because that is not correct:
Here I have an openvswitch bridge called "crowbar-br0", and with yast2-3.0.11-7.1 on 13.1, if I launch the firewall module, I can change the zone on br0 fine but if I attempt to change the zone on crowbar-br0 then I get the error dialog:
UI Syntax Error
Invalid arguments for the Label widget
Check the log file!
And y2log contains:
2014-01-13 13:21:02 <3> indian.linksys.moosehall(30549) [Ruby] modules/NetworkInterfaces.rb:1468 No such device: crowbar-br0
2014-01-13 13:21:02 <1> indian.linksys.moosehall(30549) [Ruby] yast/ops.rb:62 Index 0 is out of array size
2014-01-13 13:21:09 <1> indian.linksys.moosehall(30549) [Ruby] yast/ops.rb:62 Index 0 is out of array size
2014-01-13 13:21:09 <3> indian.linksys.moosehall(30549) [libycp] firewall/uifunctions.rb:303 Invalid arguments for the Label widget: `Label (nil)
2014-01-13 13:21:09 <2> indian.linksys.moosehall(30549) [ui] YCPDialogParser.cc(parseLabel):1213 THROW: Invalid arguments for the Label widget
2014-01-13 13:21:09 <2> indian.linksys.moosehall(30549) [ui] YCP_UI.cc(OpenDialog):585 CAUGHT: Invalid arguments for the Label widget
2014-01-13 13:21:09 <3> indian.linksys.moosehall(30549) [libycp] firewall/uifunctions.rb:303 UI::OpenDialog() failed
2014-01-13 13:21:09 <1> indian.linksys.moosehall(30549) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YOKButton for YPushButton "Close" at 0x7f53583df860 from function key F10
which looks very similar to the issue described with the firewall module in bug 853998.
(In reply to comment #13) > I suspect that this fix might not sufficient. Does it assume that all bridge > devices begin with "br"? No it doesn't. The fix repairs a bug in internal api, where device detection is already done and device name is not in game anymore.> > YCPDialogParser.cc(parseLabel):1213 THROW: Invalid arguments for the > Label widget This is main problem. An exception is raised. The exception is caught, exception handler displays the popup and the module ends. Thanks. So should I file a new bug? (In reply to comment #15) > Thanks. So should I file a new bug? yes, please. Filed as bug 858703. SUSE-RU-2015:1530-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 851769,913722,938059 CVE References: Sources used: SUSE Linux Enterprise Software Development Kit 11-SP3 (src): yast2-2.17.135.2-9.2 SUSE Linux Enterprise Server for VMWare 11-SP3 (src): yast2-2.17.135.2-9.2 SUSE Linux Enterprise Server 11-SP3 (src): yast2-2.17.135.2-9.2 SUSE Linux Enterprise Desktop 11-SP3 (src): yast2-2.17.135.2-9.2 *** Bug 848637 has been marked as a duplicate of this bug. *** |