[LbaasV2] lbaas-listener create does not fail even when lbaas VIP port is in use by nova VM

Bug #1482763 reported by Divya ChanneGowda
6
This bug affects 1 person
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-loadbalancer-create --name lb1 <subnet1>
This create a lbaas VIP port
 id | name | mac_address | fixed_ips
ce3b7dd6-d485-4db9-9b5d-7c0ca8df28b5 | loadbalancer-30d76d85-af44-4353-8852-6441ff9901a9 | fa:16:3e:3c:a0:8b | {"subnet_id": "095cab5a-c64f-4655-9900-84ffdee023e4", "ip_address": "30.40.60.2"}

Now if i try to boot a VM using this VIP port, VM boot goes through fine.

 nova boot negative_test --nic port-id=ce3b7dd6-d485-4db9-9b5d-7c0ca8df28b5

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-d485-4db9-9b5d-7c0ca8df28b5
+-----------------------+-----------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+-----------------------------------------------------------------------------------+
| admin_state_up | False |
| allowed_address_pairs | |
| binding:vif_details | {"port_filter": false} |
| binding:vif_type | ovs |
| device_id | 5c3ebb4c-d6e9-4cb7-b2d3-56fd78519b49 |
| device_owner | compute:nova |
| fixed_ips | {"subnet_id": "095cab5a-c64f-4655-9900-84ffdee023e4", "ip_address": "30.40.60.2"} |
| id | ce3b7dd6-d485-4db9-9b5d-7c0ca8df28b5 |
| mac_address | fa:16:3e:3c:a0:8b |
| name | loadbalancer-30d76d85-af44-4353-8852-6441ff9901a9 |
| network_id | a65b90fd-3659-4825-b0f3-8f1b5bee4875 |
| security_groups | bdb4b149-8b77-45fc-ad5f-d4f1c4784545 |
| status | ACTIVE |
| tenant_id | ceeb2e8e5fcd40d9a9f42a7cd691e789 |
+-----------------------+---------------------------------------

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-d485-4db9-9b5d-7c0ca8df28b5
+-----------------------+-----------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+-----------------------------------------------------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | |
| binding:vif_details | {"port_filter": false} |
| binding:vif_type | ovs |
| device_id | 27ba8ec3-c3d9-5eb2-baa4-aee774ee9da0 |
| device_owner | neutron:LOADBALANCERV2 |
| fixed_ips | {"subnet_id": "095cab5a-c64f-4655-9900-84ffdee023e4", "ip_address": "30.40.60.2"} |
| id | ce3b7dd6-d485-4db9-9b5d-7c0ca8df28b5 |
| mac_address | fa:16:3e:3c:a0:8b |
| name | loadbalancer-30d76d85-af44-4353-8852-6441ff9901a9 |
| network_id | a65b90fd-3659-4825-b0f3-8f1b5bee4875 |
| security_groups | bdb4b149-8b77-45fc-ad5f-d4f1c4784545 |
| status | ACTIVE |
| tenant_id | ceeb2e8e5fcd40d9a9f42a7cd691e789

2. Shouldn't listener-create fail when VIP port is already in use ??

Revision history for this message
Divya ChanneGowda (divya-hc) wrote :

This issue is seen only in kilo has been fixed in the master branch.
Plan to work on backporting the fix to kilo.

Changed in neutron-lbaas (Ubuntu):
assignee: nobody → Divya ChanneGowda (divya-hc)
Changed in neutron-lbaas (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.