Neutron-LBaaS v2: Pool still gets created after ListenerPoolProtocolMismatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Confirmed
|
Low
|
Unassigned |
Bug Description
1. Create a Load Balancer.
2. Create a Listener with TCP
3. Create a Pool with HTTP
4. Observe the following error: {"NeutronError": {"message": "Listener protocol TCP and pool protocol HTTP are not compatible.", "type": "ListenerPoolPr
5. List Pools.
Result: Pool still gets created after the error.
Expected: Pool should not get created if the listener and the pool protocols are not compatible.
Note: This bug occurs on any mismatch of protocols between listener and pool: TCP vs HTTP, TCP vs HTTPS, HTTP vs TCP, etc.
Log (note the creation of pool "95300d77-
2016-04-21 22:15:04.370 17603 INFO tempest.
test_create_
2016-04-21 22:15:04.370 17603 DEBUG tempest.
-Auth-Token': '<omitted>', 'Accept': 'application/json', 'Content-Type': 'application/json'}
Body: {"pool": {"name": "pool-1818041961", "protocol": "HTTP", "admin_state_up": true, "description": "pool_descripti
40568", "session_
ae-bcfb22c0163f", "lb_algorithm": "ROUND_ROBIN"}}
Response - Headers: {'content-length': '151', 'x-openstack-
21 Apr 2016 22:15:04 GMT', 'content-type': 'application/json', 'connection': 'close', 'status': '409'}
Body: {"NeutronError": {"message": "Listener protocol TCP and pool protocol HTTP are not compatible.", "type": "ListenerPoolPr
2016-04-21 22:15:04.590 17603 INFO tempest.
2016-04-21 22:15:04.590 17603 DEBUG tempest.
Body: None
Response - Headers: {'content-length': '517', 'x-openstack-
Body: {"loadbalancer": {"description": "", "admin_state_up": true, "tenant_id": "59c6e9a660b94e
For explicitness, here are the combos I've seen this bug hit on:
Listener protocol HTTP and pool protocol HTTPS are not compatible.
Listener protocol TCP and pool protocol HTTPS are not compatible.
Listener protocol HTTPS and pool protocol HTTP are not compatible.
Listener protocol TCP and pool protocol HTTP are not compatible.
Listener protocol HTTP and pool protocol TCP are not compatible.
Listener protocol HTTPS and pool protocol TCP are not compatible.
description: | updated |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: lbaas low-hanging-fruit |
Changed in neutron: | |
assignee: | nobody → Marcellin Fom Tchassem (mf6510) |
Changed in neutron: | |
assignee: | Marcellin Fom Tchassem (mf6510) → nobody |