[LbaasV2] lbaas-listener create does not fail even when lbaas VIP port is in use by nova VM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron-lbaas (Ubuntu) |
Fix Released
|
Undecided
|
Divya ChanneGowda |
Bug Description
This is a negative test case i was trying out:
neutron lbaas-loadbalan
This create a lbaas VIP port
id | name | mac_address | fixed_ips
ce3b7dd6-
Now if i try to boot a VM using this VIP port, VM boot goes through fine.
nova boot negative_test --nic port-id=
1. Should using the lbaas VIP port for nova boot be blocked??
After the VM boot, device_owner on VIP port is updated to nova:compute
neutron port-show ce3b7dd6-
+------
| Field | Value |
+------
| admin_state_up | False |
| allowed_
| binding:vif_details | {"port_filter": false} |
| binding:vif_type | ovs |
| device_id | 5c3ebb4c-
| device_owner | compute:nova |
| fixed_ips | {"subnet_id": "095cab5a-
| id | ce3b7dd6-
| mac_address | fa:16:3e:3c:a0:8b |
| name | loadbalancer-
| network_id | a65b90fd-
| security_groups | bdb4b149-
| status | ACTIVE |
| tenant_id | ceeb2e8e5fcd40d
+------
Now when i try to create a listener, this doesn't throw any error, the port owner gets updates to lbaasv2
neutron port-show ce3b7dd6-
+------
| Field | Value |
+------
| admin_state_up | True |
| allowed_
| binding:vif_details | {"port_filter": false} |
| binding:vif_type | ovs |
| device_id | 27ba8ec3-
| device_owner | neutron:
| fixed_ips | {"subnet_id": "095cab5a-
| id | ce3b7dd6-
| mac_address | fa:16:3e:3c:a0:8b |
| name | loadbalancer-
| network_id | a65b90fd-
| security_groups | bdb4b149-
| status | ACTIVE |
| tenant_id | ceeb2e8e5fcd40d
2. Shouldn't listener-create fail when VIP port is already in use ??
Changed in neutron-lbaas (Ubuntu): | |
status: | New → Fix Released |
This issue is seen only in kilo has been fixed in the master branch.
Plan to work on backporting the fix to kilo.