lbaas v2 NSX-v driver needs to improve handling Bad edge-bass request which causing ServerFault
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vmware-nsx |
New
|
Undecided
|
Unassigned |
Bug Description
NSX-v does not support multiple tenant on same subnet.
So when creating load-balancer for other tenant by admin, there will be no edge-lbaas available for this tenant.
In our current implementation, this causing Bad edge-lbass response from backend and NSX-v driver throws Server Fault.
It is better that it can generate user-level error and not create the load-balancer at all.
## tempest test trace example:
=======
ft7.4: vmware_
stderr
stdout
pythonlogging:'': {{{
2016-08-18 12:18:20,319 18865 INFO [tempest.
2016-08-18 12:18:20,320 18865 DEBUG [tempest.
Body: {"loadbalancer": {"vip_subnet_id": "18ba6dc8-
Response - Headers: {'status': '500', 'content-length': '179', 'content-location': 'http://
Body: {"NeutronError": {"message": "Driver error: Bad edge-lbaas request: No suitable Edge found for subnet 18ba6dc8-
2016-08-18 12:18:20,321 18865 INFO [vmware_
}}}
Traceback (most recent call last):
File "/opt/devtest/
vip_
File "/opt/devtest/
lb = cls.load_
File "/opt/devtest/
return self.create_
File "/opt/devtest/
resp, body = self.post(req_uri, req_post_data)
File "/opt/devtest/
return self.request(
File "/opt/devtest/
resp, resp_body)
File "/opt/devtest/
message=
tempest.
Details: Driver error: Bad edge-lbaas request: No suitable Edge found for subnet 18ba6dc8-