[qos][postgresql] neutron qos-bandwidth-limit-rule-create failed

Bug #1589969 reported by Dongcan Ye
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Slawek Kaplonski

Bug Description

Neutron version is Liberty and db backend is PostgreSQL.

Using following command to create qos ratelimit:
$ neutron qos-policy-create bw-limiter
$ neutron qos-bandwidth-limit-rule-create bw-limiter --max-kbps 3000 \
  --max-burst-kbps 300

ERROR log in neutron server:
http://paste.openstack.org/show/508633/

Tags: qos
Revision history for this message
Assaf Muller (amuller) wrote :

Assigned to Miguel for root cause analysis.

Changed in neutron:
status: New → Confirmed
importance: Undecided → Medium
tags: added: qos
Changed in neutron:
assignee: nobody → Miguel Angel Ajo (mangelajo)
Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

This reminds me of something similar we saw with an specific mysql / sqlalchemy version, it's probably time to look at this more in depth.

Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

I think this is related to :

   https://bugs.launchpad.net/neutron/+bug/1585816

Probably the incarnation of the same bug with different backends.

Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

We may want to consider switching to _get_collection in Liberty and Mitaka as in https://review.openstack.org/#/c/300055/

Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

I'm removing myself as assignee until I can get back into it. (probably past mid july)

Changed in neutron:
assignee: Miguel Angel Ajo (mangelajo) → nobody
Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

note from Ihar, verify if https://review.openstack.org/#/c/300055/ fixed it, and in such case consider backport to mitaka and libert

tags: added: liberty-backport-potential mitaka-backport-potential
Changed in neutron:
assignee: nobody → Slawek Kaplonski (slaweq)
Revision history for this message
Slawek Kaplonski (slaweq) wrote :

On latest neutron from master it looks that problem is solved.
I tried:

    admin@devstack-2:/opt/stack/neutron$ neutron qos-policy-create bw-limiter
    Created a new policy:
    +-------------+--------------------------------------+
    | Field | Value |
    +-------------+--------------------------------------+
    | description | |
    | id | 92a80865-3ac2-4c56-a800-e3fbbf429d8d |
    | name | bw-limiter |
    | rules | |
    | shared | False |
    | tenant_id | e7dbd63b709d4c6285d530a15bed2a8f |
    +-------------+--------------------------------------+
    admin@devstack-2:/opt/stack/neutron$ neutron qos-bandwidth-limit-rule-create bw-limiter --max-kbps 3000 --max-burst-kbps 300
    Created a new bandwidth_limit_rule:
    +----------------+--------------------------------------+
    | Field | Value |
    +----------------+--------------------------------------+
    | id | 859bb9a8-987c-4433-977d-f4fa262481b3 |
    | max_burst_kbps | 300 |
    | max_kbps | 3000 |
    +----------------+--------------------------------------+

and result in pgsql db:

    psql (9.3.12)
    SSL connection (cipher: DHE-RSA-AES256-GCM-SHA384, bits: 256)
    Type "help" for help.

    neutron=# select * from qos_bandwidth_limit_rules;
                  id | qos_policy_id | max_kbps | max_burst_kbps
    --------------------------------------+--------------------------------------+----------+----------------
     859bb9a8-987c-4433-977d-f4fa262481b3 | 92a80865-3ac2-4c56-a800-e3fbbf429d8d | 3000 | 300
    (1 row)

I also checked on neutron with head set to commit: 5532fb71925a2473545b0f290367234b09fc7d7f (one before https://review.openstack.org/#/c/300055/ and I had error as reported by Dongcan Ye.
So this bug is fixed now.

Changed in neutron:
status: Confirmed → Fix Committed
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

Not critical for Mitaka.

tags: removed: liberty-backport-potential
tags: removed: mitaka-backport-potential
Changed in neutron:
status: Fix Committed → 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.