Comment 16 for bug 1290486

I've run through my testing again; similar to what Marios did, except that I let the full devtest build happen, and ran "nova reboot --hard overcloud-NovaCompute0-bd3lkfo6ta2h "; I can't imagine that small difference in procedure would matter.

I don't even need to hard-kill ovsdb-server; a simple "service openvswitch-switch restart" is enough to put my setup into the error state, where traffic is seen on br-ctlplane but not the netns interface, and there are no flows listed on br-int:

    root@undercloud-undercloud-6taqd6dgghrg:~# ovs-ofctl dump-flows br-int
    NXST_FLOW reply (xid=0x4):
     cookie=0x0, duration=303.916s, table=0, n_packets=172, n_bytes=10292, idle_age=1, priority=0 actions=NORMAL

After a "service neutron-openvswitch-agent restart", the flows come back:

    root@undercloud-undercloud-6taqd6dgghrg:~# ovs-ofctl dump-flows br-int
    NXST_FLOW reply (xid=0x4):
     cookie=0x0, duration=1.124s, table=0, n_packets=2, n_bytes=160, idle_age=1, priority=3,in_port=1,vlan_tci=0x0000 actions=mod_vlan_vid:1,NORMAL
     cookie=0x0, duration=2.034s, table=0, n_packets=3, n_bytes=258, idle_age=1, priority=2,in_port=1 actions=drop
     cookie=0x0, duration=2.821s, table=0, n_packets=0, n_bytes=0, idle_age=2, priority=1 actions=NORMAL

and I can see traffic on the interface.

I'll be online just before the TripleO meeting at 1900UTC April 29th; I'll ping Marios to see if we can figure out what's different between our setups.