port status lbaas VIP binding_failed

[d032956]

trafficstars

• Title: with neutron port-show we get lbaas VIP binding_failed
• Details: We have two productive openstack locations. We have created an lbaas-loadbalancer, listener pool and pool member. The setup works fine. But the neutron port for the LBaaS VIP is in error state neutron port-show 416d722d-0179-4727-9c52-221503264ba4 +-----------------------+------------------------------------------------------------------------------------------------------------+ | Field | Value | +-----------------------+------------------------------------------------------------------------------------------------------------+ | admin_state_up | True | | allowed_address_pairs | | | binding:host_id | d00-25-b5-a0-00-b8:4d994162-4477-5837-a0d5-a26ddc3c7d1f | | binding:profile | {} | | binding:vif_details | {} | | binding:vif_type | binding_failed | | binding:vnic_type | normal | | device_id | bbcf6a35-5129-5106-b845-f7d4d636bd21 | | device_owner | network:f5lbaasv2 | | dns_assignment | {"hostname": "host-10-10-30-28", "ip_address": "10.10.30.28", "fqdn": "host-10-10-30-28.openstack.local."} | | dns_name | | | extra_dhcp_opts | | | fixed_ips | {"subnet_id": "de2321e2-da0c-4a97-8a5c-f9a553c4142b", "ip_address": "10.10.30.28"} | | id | 416d722d-0179-4727-9c52-221503264ba4 | | mac_address | fa:16:3e:82:7f:ef | | name | loadbalancer-99486fc3-0d61-4f81-bf44-0e7e599ca559 | | network_id | e9040eac-aed0-4da6-9c60-ee250e143cdd | | security_groups | 356c42ee-af87-407b-ae22-493143039424 | | status | DOWN | | tenant_id | 7f0b5f95e9f24cf3924e5aba39fddeca
  We see this for all LBaaS VIP ports .

Agent Version

agent lbaasv2 8.2.0-3.1 f5-openstack-lbaasv2-driver 8.2.0-1.1

Operating System

SUSE cloud 6

OpenStack Release

Liberty

Bug Severity

For bugs enter the bug severity level. Do not set any labels.

Severity: Severity 3 (Medium)

Severity level definitions:

1. Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
2. Severity 2 (High) : Defect is causing major obstruction of system operations.
3. Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
4. Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
5. Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.

Description

<Describe the bug in detail, steps taken prior to encountering the issue, yand a short explanation of you have deployed openstack and F5 agent>

Deployment

<Explain in reasonable detail your OpenStack deployment, the F5 OpenStack agent, and BIG-IP(s)> <Example: Single OpenStack controller with one F5 agent managing a cluster of 4 BIG-IP VEs> <Example: Three OpenStack controllers in HA, each with one standalone F5 agent managing a single BIG-IP appliance>

• Details: For enhancements, copy and paste the following template into your new issue and fill it out.

OpenStack Release

Description

[d032956]

A good solution for this topic is that neutron have a new port_binding status type = reserverd .
This solution requires a change in the neutron code . We can support you with a blueprint for this change.

[mkoderer]

I guess this is a duplicate to: https://github.com/F5Networks/f5-openstack-lbaasv2-driver/issues/127

As @d032956 mentioned - setting the state manually after the port create can cause strange behaviors if an actual port binding is needed. I would suggest to add a special "binding:vnic_type" that signals neutron that this is a reservation only.