Migrate volume fails if replication_status = 'not-capable'

[yixuan zhang]

1.Create a normal volume, without replication
2.Check the replication_status is

| replication_status | not-capable |

3:Do migrate volume
cinder migrate 04e710be-ec95-4c91-8335-c5d951f86663 ubuntu184@svc47#cinder_pool1

Migration for volume 04e710be-ec95-4c91-8335-c5d951f86663 failed: Invalid volume: Volume {'vol_id': '04e710be-ec95-4c91-8335-c5d951f86663'} status must be available or in-use, must not be migrating, have snapshots, be replicated, be part of a group and destination host/cluster must be different than the current one (HTTP 400) (Request-ID: req-6fe5a18b-ac43-4776-bf86-fcf5b6ad5136).

As check the migrate_volume api, it asked for replication_status to be None or 'disabled', The replication status 'not-capable' should support migration.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/514988

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/514988
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=6b5ff682fe45eda12da666ff26126f573478b2f0
Submitter: Zuul
Branch: master

commit 6b5ff682fe45eda12da666ff26126f573478b2f0
Author: yixuanzhang <email address hidden>
Date: Wed Oct 25 17:25:51 2017 +0800

    Fix migate_volume API with replication_status ‘not-capable’

    When migrating a volume with replication_status = 'not-capable',
    migrate_volume api will reject it because 'not-capable' isn't in
    the replication_status expected list.
    This patch fixes the issue by adding ‘not-capable’ to the expected
    replication_status list.

    Change-Id: I6bcdbd8343cca237c5f85077273a8ea18c6f534d
    Closes-Bug: #1727248

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 12.0.0.0b2 development milestone.