sm volume driver: adding backed with specified sr_uuid fails

Bug #950964 reported by Alex Meade on 2012-03-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Alex Meade

Bug Description

when doing:

nova-manage sm backend_add fake fake2

the sr_uuid is always set to None, it should be generated.

Or when doing

nova-manage sm backend_add fake fake2 sr_uuid=53d1a9cf-fb86-45cf-ae3e-6b38cec7cdb4

it should update the backend with the specified sr_uuid or prompt to add one with that sr_uuid.

Currently, sr_uuid is basically ignored.

Alex Meade (alex-meade) on 2012-03-09
Changed in nova:
assignee: nobody → Alex Meade (alex-meade)
status: New → In Progress

Submitter: Jenkins
Branch: master

commit 77495cfed17f12f225e11fbc10e0f8db516dadf2
Author: Alex Meade <email address hidden>
Date: Thu Mar 8 21:56:56 2012 +0000

    Fix nova-manage backend_add with sr_uuid

    Fixes bug 950964

    Remove FIXME in db.sm_backend_conf_get_by_sr
    Add first() to sm_backend_conf_get_by_sr query
    Change db/ to call correct impl method
    Have nova-manage generate an actuall sr_uuid instead of always 'None'
    Actually update backend values when specifying uuid

    Change-Id: I620da4563d8c936b5a072c4683ae145280104fc2

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-03-20
Changed in nova:
milestone: none → essex-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers