Fixes OPENSTACK-1106 Not a direct fix for this issue. The root cause is that the upstream delete the db entry before the agent actually deletes the listener and cleans up the vif port on vrs and we are seeing a racecondition when we do listener delete and loadbalancer delete back to back. We are seeing an issue in update_port where we try to process_port_sg_group on the port and by then lb_delete triggered delete_port has deleted the port and process_port_sg raises an exception that vport does not exist and we end up not cleaning up the port on vrs. Call process_port_sg in update_port only if the old and new requested port sg doesn't match. Since in the lbaas case, the sg doesn't change during listener_delete, process_port_sg is skipped and we won't hit the vport not exist case. But the actual fix needs to go upstream. But this fix is good to have even otherwise this issue.
Fixes OPENSTACK-1106
Not a direct fix for this issue. The root cause is that the upstream delete the db entry before the
agent actually deletes the listener and cleans up the vif port on vrs and we are seeing a racecondition
when we do listener delete and loadbalancer delete back to back.
We are seeing an issue in update_port where we try to process_port_sg_group on the port and by then
lb_delete triggered delete_port has deleted the port and process_port_sg raises an exception that
vport does not exist and we end up not cleaning up the port on vrs.
Call process_port_sg in update_port only if the old and new requested port sg doesn't match.
Since in the lbaas case, the sg doesn't change during listener_delete, process_port_sg is skipped and
we won't hit the vport not exist case. But the actual fix needs to go upstream.
But this fix is good to have even otherwise this issue.

Change-Id: Ibdc9a9d48789cc66ecd580364563945a3f247478
Closes-Bug: OPENSTACK-1106

nuagenetworks/nuage-openstack-neutron,naveensan1/nuage-openstack-neutron,nuagenetworks/nuage-openstack-neutron,naveensan1/nuage-openstack-neutron