Cinder

cinder-manage import DB should check nova DB level

Bug #1052598 reported by John Griffith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Critical
John Griffith
Cinder 2012.2 "folsom"

Bug Description

The cinder-manage import DB to switch from nova-volume to cinder is intended to be used only if you've already upgraded nova-volume to Folsom. It assumes this which is not such a good idea. We should add a check of the nova-volume version and if it's not up to date, present an appropriate error messages.

As it stands now, the import just fails with various import errors that likely won't make sense to most people.

John Griffith (john-griffith)
Changed in cinder:
milestone: none → folsom-rc1
importance: Undecided → Critical
assignee: nobody → John Griffith (john-griffith)
Thierry Carrez (ttx)
Changed in cinder:
milestone: folsom-rc1 → none
tags: added: folsom-rc-potential
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/13223

Changed in cinder:
status: New → In Progress
Thierry Carrez (ttx)
Changed in cinder:
milestone: none → folsom-rc2
tags: removed: folsom-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (milestone-proposed)

Fix proposed to branch: milestone-proposed
Review: https://review.openstack.org/13320

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

Reviewed: https://review.openstack.org/13320
Committed: http://github.com/openstack/cinder/commit/f8d49ae61021e1ad2aaaf2555c4954ba0e3dc026
Submitter: Jenkins
Branch: milestone-proposed

commit f8d49ae61021e1ad2aaaf2555c4954ba0e3dc026
Author: John Griffith <email address hidden>
Date: Tue Sep 18 13:29:20 2012 -0600

    Add nova migrate_version check to cinder import

    Cinder-manage migrate import only works from Nova/Folsom--->Cinder/Folsom
    this change adds an explicit check of the nova migrate_version (133)
    to make sure we have all of the volume id/uuid changes that are needed
    to be compatable, and presents an error message if that's not the case.

    Addresses bug #1052598

    Change-Id: I7f32cf35e33320f4348b7bc44a8e92b5716b71d8
    (cherry picked from commit 321d32379cd6044378f2f9c32c068de18f514df5)

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

Reviewed: https://review.openstack.org/13223
Committed: http://github.com/openstack/cinder/commit/321d32379cd6044378f2f9c32c068de18f514df5
Submitter: Jenkins
Branch: master

commit 321d32379cd6044378f2f9c32c068de18f514df5
Author: John Griffith <email address hidden>
Date: Tue Sep 18 13:29:20 2012 -0600

    Add nova migrate_version check to cinder import

    Cinder-manage migrate import only works from Nova/Folsom--->Cinder/Folsom
    this change adds an explicit check of the nova migrate_version (133)
    to make sure we have all of the volume id/uuid changes that are needed
    to be compatable, and presents an error message if that's not the case.

    Addresses bug #1052598

    Change-Id: I7f32cf35e33320f4348b7bc44a8e92b5716b71d8

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: folsom-rc2 → 2012.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.