On Thu, Mar 29, 2018 at 4:37 PM, Francesco Romani <fromani@redhat.com> wrote:
Hi developers,
we had another network CI failure while testing unrelated changes:
http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/22708/consol...
12:20:19 self = <network.integration.link_bond_test.LinkBondTests testMethod=test_bond_clear_arp_ip_target> 12:20:19 12:20:19 def test_bond_clear_arp_ip_target(self): 12:20:19 OPTIONS_A = { 12:20:19 'mode': '1', 12:20:19 'arp_interval': '1000', 12:20:19 'arp_ip_target': '192.168.122.1'} 12:20:19 OPTIONS_B = { 12:20:19 'mode': '1', 12:20:19 'arp_interval': '1000'} 12:20:19 12:20:19 with bond_device() as bond: 12:20:19 > bond.set_options(OPTIONS_A) 12:20:19 12:20:19 network/integration/link_bond_test.py:171:
Could please some network developer have a look?
Bests,
-- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
So sorry for this noise. I've prematurely merged a patch that moved tests around, and mistakenly approved a CI failure there, which blocked the real problem. https://gerrit.ovirt.org/#/c/89562/ (merged recently) should solve your reported problem. Note, however, that we still have a problem with ovs-vsctl randomly hanging our integration tests since we've upgraded to openvswitch-2.9 last weekend.