yahoo-eng-team team mailing list archive

[OpenStack Infra <1533687@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/269050
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c82f0021d50a19861da12e112fb8756d49d1b804
Submitter: Jenkins
Branch:    master

commit c82f0021d50a19861da12e112fb8756d49d1b804
Author: Sergey Belous <sbelous@xxxxxxxxxxxx>
Date:   Mon Jan 18 16:37:06 2016 +0300

    Add relationship between port and floating ip
    
    We need to have the relationship between port and floating ip, because updating
    quota will happen when the event "after_delete" occurs. And current cascade
    removal of the floating ip does not cause the event "after_delete" for floating
    ip. The cascade on the ORM-level "delete" must be added.
    
    Closes-bug: #1533687
    Change-Id: Id414cf20069563085737fee5ddce94b1bf2f912d


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1533687

Title:
  Quota info in DB for floatingip is not updated immediately

Status in neutron:
  Fix Released

Bug description:
  The records in quotausages table for floatingip are not updated immediately after delete some (or all) floatingips.
  For example, if we set quota for floatingip to 5, create 5 floatingips and remove all of them, after that we can't create new floatingip:
  The error "Quota exceeded for resources: ['floatingip']." occurs.
  And at this time in mysql db we can see following:
  mysql> select * from quotausages;
  +----------------------------------+------------+-------+--------+----------+
  | tenant_id                        | resource   | dirty | in_use | reserved |
  +----------------------------------+------------+-------+--------+----------+
  | fae4b729e0d543199331d6be300074fc | floatingip |     0 |      5 |        0 |
  | fae4b729e0d543199331d6be300074fc | network    |     0 |      1 |        0 |
  +----------------------------------+------------+-------+--------+----------+

  Steps to reproduce:
  1. $ neutron quota-update --floatingip 5
  2. $ for i in $(seq 1 5); do neutron floatingip-create public; done
  3. Try to create another one floatingip (should not be created):
  $ neutron floatingip-create public
  Quota exceeded for resources: ['floatingip'].
  4. $ for ip in $(neutron floatingip-list -f csv -c id --quote=none | grep -v id); do neutron floatingip-delete $ip done
  5. Try to create another one floatingip:
  $ neutron floatingip-create public
  Quota exceeded for resources: ['floatingip'].
  6. Check quotas info in db:
  mysql> use neutron
  mysql> select * from quotausages;

  Full log here: http://paste.openstack.org/show/483767/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533687/+subscriptions