On 12/02/2015 09:23, Ramon Medeiros wrote:
On 02/11/2015 09:25 PM, Christy Perez wrote:
Hi Team,
i got this issue on https://github.com/kimchi-project/kimchi/issues/556. What we can do:
1) The fix seems to be upstream. But not sure if it will be available soon What's the fix? I'm noticing that if I delete the bridge myself, then re-run the test, it stays after failure. I'm guessing the fix would be
On 02/11/2015 11:23 AM, Ramon Medeiros wrote: that the bridge should be deleted by libvirt since it's created by libvirt, but I'd like to see what you're referencing here.
I think deleting a bridge is too intrusive to the system. Today, when we created the default network, no bridge is passed on xml. What about create a new virbrX bridge and pass it to libvirt?
Create a bridge seems too intrusive for me too. If it is a libvirt issue we should wait for the libvirt fix. As you said Kimchi does not specify the bridge when activating the default network.
2) Run a check, like we do for subnet, to see if it's already created. If not, we can created it and pass to libvirt.
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel