sm volume driver: adding backed with specified sr_uuid fails
Bug #950964 reported by
Alex Meade
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
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=
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.
Changed in nova: | |
assignee: | nobody → Alex Meade (alex-meade) |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → essex-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/5102 github. com/openstack/ nova/commit/ 77495cfed17f12f 225e11fbc10e0f8 db516dadf2
Committed: http://
Submitter: Jenkins
Branch: master
commit 77495cfed17f12f 225e11fbc10e0f8 db516dadf2
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 conf_get_ by_sr query py:sm_backend_ conf_get_ by_sr to call correct impl method
Add first() to sm_backend_
Change db/api.
Have nova-manage generate an actuall sr_uuid instead of always 'None'
Actually update backend values when specifying uuid
Change-Id: I620da4563d8c93 6b5a072c4683ae1 45280104fc2