What | Removed | Added |
---|---|---|
CC | knut.anderssen@suse.com |
(In reply to Charles Arnold from comment #7) > (In reply to Oliver Kurz from comment #6) > > (In reply to Charles Arnold from comment #5) > > > I think it is possible that 'yast2 virtualization' (yast2-vm) is failing to > > > create a bridge. If so, the problem is likely in the yast2-network code > > > because the yast2-vm code is very simple and just calls into yast2-network > > > to do the bridge creation. > > > > > > A simple 'ip addr' on the host would confirm if a bridge is present. > > > > Could you please state what your plans are regarding this? It should not be > > hard to reproduce the issue as it is reproducible every time. Also running > > openQA tests yourself or investigating interactively should not be too hard. > > yast2-vm requests a bridge device to be created with the following code: > > Lan.Read(:cache) > Lan.ProposeVirtualized > Lan.Write > > This is not working on Tumbleweed (tested on 20190126). The code being called > is in yast2-network. This used to work. Either yast2-vm needs to do it > differently now or something is broken in yast2-network. > > Michal, > Could you take a look at this? I tested in TW with build 20190512 and works as expected, so the bridge br0 was created correctly.