Bug 1412744
Summary: | Load balancer v2 in PENDING* state cannot be deleted | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Ondrej <ochalups> |
Component: | openstack-neutron-lbaas | Assignee: | Nir Magnezi <nmagnezi> |
Status: | CLOSED WONTFIX | QA Contact: | Toni Freger <tfreger> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 10.0 (Newton) | CC: | amuller, apevec, giondog, lhh, nyechiel, ochalups |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-25 12:51:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ondrej
2017-01-12 16:36:59 UTC
Not being able to delete a load balancer in a PENDING state is intended behavior. It seems like the issue here is that the load balancer was stuck in PENDING. Can you confirm this? If so, can you clarify how the balancer got stuck in PENDING? The neutron-lbaasv2-agent was down because of wrong device_driver. Loadbalancers created before we were able to fix the right driver and bring the agent up were stuck in PENDING_CREATE. We're not able to get rid of them now. I tried to cheat it by changing the loadbalancer status in neutron db to ACTIVE, but that didn't work. (In reply to Ondrej from comment #2) > The neutron-lbaasv2-agent was down because of wrong device_driver. > Loadbalancers > created before we were able to fix the right driver and bring the agent up > were stuck in PENDING_CREATE. We're not able to get rid of them now. > I tried to cheat it by changing the loadbalancer status in neutron db to > ACTIVE, but that didn't work. Would this be a reproducer then? 1) Install LBaaS v2, create a load balancer successfully 2) Shut down the LBaaS v2 agent 3) Create a new load balancer 4) Start up the LBaaS v2 agent again Observe that the load balancer is stuck in PENDING_* and cannot be deleted. Correct? Yes, exactly. Hello, any update on this? Was it fixed? I just got the same error Assigned to Nir for RCA. As the Michael (the PTL) said[1], it's by design to not allow actions on load balancers in PENDING_* states. You may simply delete the row for that specific loadbalancer from the database, but there is no mechanism to move those to a different state. If any, the issue I see here is the fact that the client request for loadbalancer creation was not rejected when the agent is down, but that would really depend on how it was implemented (synchronous or asynchronous). In any case, this bug is against loadbalanacers that got stuck in PENDING state. BTW, such scenario is handled in Octavia, but not in the legacy implementation. [1] https://bugs.launchpad.net/octavia/+bug/1498130/comments/7 |