Share migration tempest test fail on driver optimized migration

[Rodrigo Barbieri]

Currently, if driver implements optimized migration as per driver interface, tempest test "test_migration_completion_empty_v2_15" waits forever for task_state "data_copying_completed" while task_state is in fact "migration_driver_phase1_done".

Tempest test "test_migration_empty_v2_5" fails in validation of 'host' field of migrated share. It is not explicit if share should return the model update with the updated destination host or expect manila code to update it.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/332267
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=c7fe51e79b63f3e0556cce19a48252aaee317823
Submitter: Jenkins
Branch: master

commit c7fe51e79b63f3e0556cce19a48252aaee317823
Author: Rodrigo Barbieri <email address hidden>
Date: Wed Aug 24 22:01:31 2016 -0300

    Fix Share Migration improper behavior for drivers

    Tempest tests were not appropriate for driver-assisted migration,
    so this was fixed.

    Also, improved docstrings and fixed workflow for drivers when
    implementing 2-phase migration to be accurate with tempest and
    handle AZs, which were previously locked to the source share's
    AZ.

    Driver-assisted migration now creates an additional
    share instance to better handle and support driver methods.

    Updated allow_access and deny_access APIs to allow users to mount
    migrating shares before issuing 'migration-complete'.

    APIImpact

    Closes-bug: #1594922
    Change-Id: If4bfaf7e9d963b83c13a6fea241c2eda14f7f409

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/manila 3.0.0.0b3 development milestone.