fixed ips and floating ips can't be synced properly

Bug #1214523 reported by Liyingjun
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Andrew Laski

Bug Description

fixed ips and floating ips can't be synced properly because they're tracked per user in the quota table but they're not tied to a user so it's not feasible to grab a count of how many are being used by any particular user. So the quota_usages table can get into a bad state if it sync with user level..

I think we could make the user_id column=NULL when creating the quota usage and reservation, so the usages for fixed_ips and floating_ips will be synced within the project.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/42966

Changed in nova:
assignee: nobody → Liyingjun (liyingjun)
status: New → In Progress
Changed in nova:
assignee: Liyingjun (liyingjun) → Andrew Laski (alaski)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/42966
Committed: http://github.com/openstack/nova/commit/5a8363adacec44e84a4f6d6e4fa24680b22072eb
Submitter: Jenkins
Branch: master

commit 5a8363adacec44e84a4f6d6e4fa24680b22072eb
Author: liyingjun <email address hidden>
Date: Wed Aug 21 02:26:40 2013 +0800

    Fixes sync issue for user level resources

    fixed/floating ips and networks can't be synced properly because they're
    tracked per user in the quota table but they're not tied to a user so
    it's not feasible to grab a count of how many are being used by any
    particular user. So the quota_usages table can get into a bad state if
    it sync with user level.
    Sync these resources with project level, and set quota with project
    level to solve the problem.

    Fixes bug 1214523

    Change-Id: Icd94e95fb706ee90e0737e85cfa50f05ff3c0ff8

Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
Liyingjun (liyingjun) wrote :

There is still an additional bug related.
In the case, if a normal user created a fixed_ip/floating_ip, then the fixed_ip/floating_ip is deleted by admin, a new reservation/usage record will be created in the db, and it should be the right case that the usage for fixed_ip/floating_ip of the user decreased.
See exactly: https://github.com/openstack/nova/blob/master/nova/network/floating_ips.py#L277, https://github.com/openstack/nova/blob/master/nova/network/floating_ips.py#L289,
https://github.com/openstack/nova/blob/master/nova/network/manager.py#L869,
https://github.com/openstack/nova/blob/master/nova/network/manager.py#L939

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/43583

Thierry Carrez (ttx)
Changed in nova:
milestone: none → havana-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: havana-3 → 2013.2
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.