We shouldn't update the devices_to_filter for port id's belonging to VM's
hosted on other ESX hosts.
In the scalability setup we have observed that due to unavailability of
resources on a given ESX nova delete the VM's and neutron eventually deletes
the port associated to that VM from DB, since OVSvApp agent running on other
ESX host tries to delete the flows for that port it won't be able to find in
neutron DB and get_ports_details_list RPC throws exception and stuck in loop.
Reviewed: https:/ /review. openstack. org/227497 /git.openstack. org/cgit/ openstack/ networking- vsphere/ commit/ ?id=61a9384dcee fc2f542985b30e0 a1a9ba60d49b1b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 61a9384dceefc2f 542985b30e0a1a9 ba60d49b1b
Author: Romil Gupta <email address hidden>
Date: Thu Sep 24 11:51:29 2015 -0700
Fix device_create method in ovsvapp_agent
We shouldn't update the devices_to_filter for port id's belonging to VM's
hosted on other ESX hosts.
In the scalability setup we have observed that due to unavailability of details_ list RPC throws exception and stuck in loop.
resources on a given ESX nova delete the VM's and neutron eventually deletes
the port associated to that VM from DB, since OVSvApp agent running on other
ESX host tries to delete the flows for that port it won't be able to find in
neutron DB and get_ports_
Change-Id: I912d32c33c3f36 d87df6539f925f1 8a8ab1890fc
Closes-Bug: 1499504