Public bug reported:

If all neutron-lbaasv2-agent are down at a given time, you could get
some loadbalancers stucked in PENDING_CREATE.

With CLI tools it is impossible to delete these resources:

(neutron) lbaas-loadbalancer-delete 5173ac41-194d-4d0c-b833-657b728c469d
Invalid state PENDING_CREATE of loadbalancer resource 
5173ac41-194d-4d0c-b833-657b728c469d
Neutron server returns request_ids: ['req-970a6338-b0d0-4bcc-9108-ec94360b45e2']

Even deleting this loadbalancer from the database with mysql commands
does not clean it completely.

the VIP port also needs to be deleted, not possible with API because I get:
(neutron) port-delete 264f6125-ef0f-46ab-84b6-79da2d00eb28
Port 264f6125-ef0f-46ab-84b6-79da2d00eb28 cannot be deleted directly via the 
port API: has device owner neutron:LOADBALANCERV2.
Neutron server returns request_ids: ['req-ed4718e0-e8a3-4c53-9416-de97cc73230f']

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

- 
- If all neutron-lbaasv2-agent are down at a given time, you could get some 
loadbalancers stucked in PENDING_CREATE.
+ If all neutron-lbaasv2-agent are down at a given time, you could get
+ some loadbalancers stucked in PENDING_CREATE.
  
  With CLI tools it is impossible to delete these resources:
  
  (neutron) lbaas-loadbalancer-delete 5173ac41-194d-4d0c-b833-657b728c469d
  Invalid state PENDING_CREATE of loadbalancer resource 
5173ac41-194d-4d0c-b833-657b728c469d
  Neutron server returns request_ids: 
['req-970a6338-b0d0-4bcc-9108-ec94360b45e2']
+ 
+ Even deleting this loadbalancer from the database with mysql commands
+ does not clean it completely.
+ 
+ the VIP port also needs to be deleted, not possible with API because I get:
+ (neutron) port-delete 264f6125-ef0f-46ab-84b6-79da2d00eb28
+ Port 264f6125-ef0f-46ab-84b6-79da2d00eb28 cannot be deleted directly via the 
port API: has device owner neutron:LOADBALANCERV2.
+ Neutron server returns request_ids: 
['req-ed4718e0-e8a3-4c53-9416-de97cc73230f']

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1673754

Title:
  LBaaSv2: Cannot delete loadbalancer in PENDING_CREATE

Status in neutron:
  New

Bug description:
  If all neutron-lbaasv2-agent are down at a given time, you could get
  some loadbalancers stucked in PENDING_CREATE.

  With CLI tools it is impossible to delete these resources:

  (neutron) lbaas-loadbalancer-delete 5173ac41-194d-4d0c-b833-657b728c469d
  Invalid state PENDING_CREATE of loadbalancer resource 
5173ac41-194d-4d0c-b833-657b728c469d
  Neutron server returns request_ids: 
['req-970a6338-b0d0-4bcc-9108-ec94360b45e2']

  Even deleting this loadbalancer from the database with mysql commands
  does not clean it completely.

  the VIP port also needs to be deleted, not possible with API because I get:
  (neutron) port-delete 264f6125-ef0f-46ab-84b6-79da2d00eb28
  Port 264f6125-ef0f-46ab-84b6-79da2d00eb28 cannot be deleted directly via the 
port API: has device owner neutron:LOADBALANCERV2.
  Neutron server returns request_ids: 
['req-ed4718e0-e8a3-4c53-9416-de97cc73230f']

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1673754/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to