volume transfer doesn't include policy checks

Bug #1187910 reported by John Griffith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
John Griffith

Bug Description

Volume transfer functionality should have policy checks to enable/disable specific users. Currently there's no policy rules or policy checks implemented in the transfer api.

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

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

Changed in cinder:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/31857
Committed: http://github.com/openstack/cinder/commit/db40ad11f1b8fa60ea9c0d69240487ec84df9341
Submitter: Jenkins
Branch: master

commit db40ad11f1b8fa60ea9c0d69240487ec84df9341
Author: John Griffith <email address hidden>
Date: Wed Jun 5 13:57:29 2013 -0600

    Add policy checking for transfer create/accept.

    This patch adds policy checks for transfer create/accept
    as well as adding the associated default policy. In addition
    we add the wrap in the volume/api accept_transfer method.

    Fixes bug: 1187910

    Change-Id: I599ac0a95cea1605380d4595a1f21023fbcfb6f1

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in cinder:
milestone: havana-2 → 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.