Radware LBaaS v2 driver - member deletion bug

[Evgeny Fedoruk]

When deleting a member from LBaaS listener's pool, member is deleted, but Radware back-end system still have it.

The problem is at Radware LBaas v2 driver which reports members/listeners with PENDING-DELETE status as a living object on a payload to the back-end system

The solution is to filter out of a payload objects that should be deleted.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/175203

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/175203
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=bf6d10bdc4ca94b6b525e0fcefbff8ca907ff237
Submitter: Jenkins
Branch: master

commit bf6d10bdc4ca94b6b525e0fcefbff8ca907ff237
Author: Evgeny Fedoruk <email address hidden>
Date: Sun Apr 19 03:45:57 2015 -0700

    Fixing LBaaS object deletion on Radwrae back-end

    Fixing bug when PENDING-DELETE listeners and members
    were entering Radware's back-end payload

    Change-Id: I46e958b8543ac72cd6987baa45e201f562b8b929
    Closes-Bug: 1445896