Comment 4 for bug 1358554

I was going to start instrumenting things to help figure this out, but from going through the devstack logs, I can see that there's a call to treat_devices_added_or_updated() that is not finding the port_id in the plugin.

Some quick snippets from the q-agt.log:

Processing port: 3a92ebef-520d-4c68-8b1f-93ade0783625 treat_devices_added_or_updated

 Port 3a92ebef-520d-4c68-8b1f-93ade0783625 updated. Details: {u'profile': {}, u'admin_state_up': True, u'network_id': u'a3f1feb8-4937-4d74-9c45-b2939385b49e', u'segmentation_id': 1004, u'device_owner': u'network:router_interface_distributed', u'physical_network': None, u'mac_address': u'fa:16:3e:a1:48:44', u'device': u'3a92ebef-520d-4c68-8b1f-93ade0783625', u'port_id': u'3a92ebef-520d-4c68-8b1f-93ade0783625', u'fixed_ips': [{u'subnet_id': u'ac5a54af-f1e5-413b-9fed-a771d49f9d2b', u'ip_address': u'10.100.0.1'}], u'network_type': u'vxlan'}

 Assigning 3 as local vlan for net-id=a3f1feb8-4937-4d74-9c45-b2939385b49e

 'ovs-vsctl', '--timeout=10', 'set', 'Port', 'qr-3a92ebef-52', 'tag=3'

 update_device_up
 {couple of minutes}
 update_device_down

Then a few minutes later:

Processing port: 3a92ebef-520d-4c68-8b1f-93ade0783625 treat_devices_added_or_updated

 Device 3a92ebef-520d-4c68-8b1f-93ade0783625 not defined on plugin

 'ovs-vsctl', '--timeout=10', 'set', 'Port', 'qr-3a92ebef-52', 'tag=4095'

I'll continue looking tomorrow.