[stable/newton] LBaaS statistics cli doesn't show updated values.

Bug #1636380 reported by Sujai
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
He Qing

Bug Description

I have enabled Octavia in my stable/newton setup and verifying LBaaS services.

The cli command "neutron lbaas-loadbalancer-stats" is not showing the updated values.All the
statistics field's values are zero.

vmware@cntr1:/opt/stack/logs$ neutron lbaas-loadbalancer-stats 663350ad-d515-423b-add1-11b38b14356b
+--------------------+-------+
| Field | Value |
+--------------------+-------+
| active_connections | 0 |
| bytes_in | 0 |
| bytes_out | 0 |
| total_connections | 0 |
+--------------------+-------+

However, stats collected using Octavia API is having updated values.

vmware@cntr1:/opt/stack/logs$ curl -H "X-Auth-Token:008e1258cc294f9eb3a99df7b2da3e88" http://localhost:9876/v1/loadbalancers/663350ad-d515-423b-add1-11b38b14356b/listeners/a7743e61-a507-4300-81ad-3da3c9046511/stats
{"bytes_in": 89520, "total_connections": 1119, "active_connections": 0, "bytes_out": 402840}

Loadbalancer Info:

vmware@cntr1:/opt/stack/logs$ neutron lbaas-loadbalancer-show 663350ad-d515-423b-add1-11b38b14356b
+---------------------+------------------------------------------------+
| Field | Value |
+---------------------+------------------------------------------------+
| admin_state_up | True |
| description | |
| id | 663350ad-d515-423b-add1-11b38b14356b |
| listeners | {"id": "a7743e61-a507-4300-81ad-3da3c9046511"} |
| name | test-lb |
| operating_status | ONLINE |
| pools | {"id": "3a5e4090-fb2c-49e6-b209-ac5c6fb6fd21"} |
| provider | octavia |
| provisioning_status | PENDING_UPDATE |
| tenant_id | c9b2dc6e087e4aa9913701f48d520914 |
| vip_address | 50.0.0.11 |
| vip_port_id | 540c4137-ab17-42d1-9e21-a82793607772 |
| vip_subnet_id | ae311056-b856-464d-a706-bd26f33917a8 |
+---------------------+------------------------------------------------+

vmware@cntr1:/opt/stack/logs$ neutron lbaas-listener-list
+--------------------------------------+--------------------------------------+--------------+----------+---------------+----------------+
| id | default_pool_id | name | protocol | protocol_port | admin_state_up |
+--------------------------------------+--------------------------------------+--------------+----------+---------------+----------------+
| a7743e61-a507-4300-81ad-3da3c9046511 | 3a5e4090-fb2c-49e6-b209-ac5c6fb6fd21 | test-lb-http | TCP | 8000 | True |
+--------------------------------------+--------------------------------------+--------------+----------+---------------+----------------+

Please fix it.

Sujai (sujai)
no longer affects: octavia
Revision history for this message
Michael Johnson (johnsom) wrote :

This is an issue in neutron-lbaas (as discussed in the bug showing the octavia API returns the correct results). The octavia neutron-lbaas driver is not correctly pulling this information from Octavia and/or the event streamer should be updated to handle the stats in addition to the health status.

This is also not a devstack bug, but I cannot remove that project from this bug.

affects: octavia → neutron
Changed in neutron:
importance: Undecided → High
status: New → Triaged
Sujai (sujai)
no longer affects: devstack
He Qing (tsinghe-7)
Changed in neutron:
assignee: nobody → He Qing (tsinghe-7)
Revision history for this message
He Qing (tsinghe-7) wrote :
Changed in neutron:
status: Triaged → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-lbaas 11.0.0.0b1

This issue was fixed in the openstack/neutron-lbaas 11.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-lbaas 9.2.2

This issue was fixed in the openstack/neutron-lbaas 9.2.2 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-lbaas ocata-eol

This issue was fixed in the openstack/neutron-lbaas ocata-eol release.

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.