xen storage manager: create volume fails after uuid changes in nova-volume

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

Bug Description

1) SM still assumes volume id to be an integer.
2) Parameters to the create_vdi function have changed, causing the call from storage manager code to fail.

Changed in nova:
assignee: nobody → Renuka Apte (renukaapte)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/7954
Committed: http://github.com/openstack/nova/commit/152cf6f592a40b54cfb8b0132aee944e5533d54d
Submitter: Jenkins
Branch: master

commit 152cf6f592a40b54cfb8b0132aee944e5533d54d
Author: Renuka Apte <email address hidden>
Date: Tue May 29 11:54:35 2012 -0700

    xensm: Fix xensm volume driver after uuid changes

    Fixes Bug 1013436
    Minor fixes after uuid in volumes were changed from
    integers.
    The parameters passed to create_vdi have changed, so
    modify the call from SM code accordingly

    Change-Id: I3d61f0221b23bba9a9e218209d5293be8960e2e2

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