cinder-manage migrate should be removed in Havana

Bug #1187134 reported by Jay Bryant on 2013-06-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Jay Bryant

Bug Description

The cinder-manage migrate commands were intended to be used only with Nova-Folsom-->Cinder-Folsom Volumes. Migrating with Grizzly or newer volumes hasn't been tested. So, we should remove this option from cinder-manage in Havana.

Jay Bryant (jsbryant) on 2013-06-03
Changed in cinder:
assignee: nobody → Jay Bryant (jsbryant)
Changed in cinder:
status: New → Triaged
importance: Undecided → Medium
milestone: none → havana-2

Fix proposed to branch: master

Changed in cinder:
status: Triaged → In Progress

Submitter: Jenkins
Branch: master

commit f6064e729d20464857c7136ed7b8ab8548c4f561
Author: Jay S. Bryant <email address hidden>
Date: Fri Jun 14 18:30:10 2013 -0500

    Remove the 'migrate' option from cinder-manage

    The 'migrate' option was only appropriate for use migrating
    databases for volumes from Nova-Folsom-->Cinder-Folsom. The
    code hasn't been tested since.

    Given the above facts, this commit removes the migrate code from
    cinder-manage. The man page for cinder-manage was already
    updated to remove the option in a previous commit.

    (fixes bug #1187134)

    Change-Id: I7bf378cd4b0dd4f6d1bdf475b826a59a31112638

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-07-17
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-2 → 2013.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers