Unmanage API allows schedule unmanaging of share that could not be managed

[Valeriy Ponomaryov]

For the moment "manage/unmanage" operation is allowed only for driver mode without handling of share servers.

But "unmanage" API allows us to schedule unamanging of share that was created on top of share server. It leads to change of sahre status "UNMANAGE_ERROR". It should be restricted on API side.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit a0703047d52b700ef8917996dd45ca3fb16e5f5d
Author: Valeriy Ponomaryov <email address hidden>
Date: Fri Mar 20 20:58:17 2015 +0200

    Add share state verification for API 'unmanage'

    Shares with transitional states like 'creating' or 'deleting' should not be
    allowed to be unmanaged.
    For the moment "manage/unmanage" operation is allowed only for driver mode
    without handling of share servers. So, API operations against shares created
    on top of share servers should be restricted on API level.

    Change-Id: I73b554448eadcb96ef00f44535014e14dea91472
    Closes-Bug: #1434642
    Closes-Bug: #1434511