Public bug reported:
As an admin user:
1. Create a Load balancer.
2. Create a pool for the load balancer.
3. Add a member to the pool.
4. Delete the pool.
5. Check Load balancer status.
Result: Load balancer status will be set to "PENDING_UPDATE" for more
than 30 mins.
Expected Result: Load balancer status should be immediately set to
ACTIVE or "PENDING_UPDATE" should be a relatively short wait.
note: Deleting a pool from a load balancer, which has no members, is
relatively fast. It seems that when the pool has members, the delete
pool takes a significant amount of time.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: lbaasv2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1572222
Title:
Neutron-LBaaS v2: Deleting pool that has members from load balancer
takes a long time
Status in neutron:
New
Bug description:
As an admin user:
1. Create a Load balancer.
2. Create a pool for the load balancer.
3. Add a member to the pool.
4. Delete the pool.
5. Check Load balancer status.
Result: Load balancer status will be set to "PENDING_UPDATE" for more
than 30 mins.
Expected Result: Load balancer status should be immediately set to
ACTIVE or "PENDING_UPDATE" should be a relatively short wait.
note: Deleting a pool from a load balancer, which has no members, is
relatively fast. It seems that when the pool has members, the delete
pool takes a significant amount of time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1572222/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
