quota commits to wrong project/user if we use admin user to verify a resized instance of other's

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

Bug Description

it is that, if the confirmation is launched through admin user,
then the project_id and user_id in context are all admin's, which
result in reservations in DB are also have wrong project_id and
user_id, when these reservations are committed, the quotas usage of
the instance's project/user will become wrong eventually.

this bug can be reproduced both in stable havana and master.
so we need to backport this fix patch to stable havana.

this bug is similar as Bug #1271429.

wangpan (hzwangpan)
description: updated
wangpan (hzwangpan)
Changed in nova:
assignee: nobody → wangpan (hzwangpan)
Changed in nova:
status: New → In Progress
Chris Behrens (cbehrens)
tags: added: icehouse-rc-potential
Thierry Carrez (ttx)
tags: added: icehouse-backport-potential
removed: icehouse-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/82538
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bf936b4e5821ef55260ff714a8e91b736c37dbd6
Submitter: Jenkins
Branch: master

commit bf936b4e5821ef55260ff714a8e91b736c37dbd6
Author: Chris Behrens <email address hidden>
Date: Mon Mar 24 16:20:39 2014 +0000

    Use project/user from instance for quotas

    If an admin confirms a resize, a periodic task auto-confirms a resize,
    or if an admin reverts a resize, these should all use the instance
    project/user for quota updates.

    Closes-bug: 1271429
    Closes-bug: 1278686
    Closes-bug: 1278695

    Change-Id: I1e128cd4035d0140e35582de795eb4d6fb8603f2

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → juno-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: juno-1 → 2014.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.