OVO destroy methods don't update the instance

[Gorka Eguileor]

None of the Versioned Objects destroy methods we have update the instance fields, so after doing a destroy on an instance the status, deleted, and deleted_at fields will still be the same as they were before, leaving the instance in an inconsistent state.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/344223
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b03f539e6e106480f0caea2f561757e0049f9505
Submitter: Jenkins
Branch: master

commit b03f539e6e106480f0caea2f561757e0049f9505
Author: Gorka Eguileor <email address hidden>
Date: Tue Jul 19 12:37:02 2016 +0200

    Update OVO instance on destroy method call

    None of the Versioned Objects destroy methods we have update the
    instance fields, so after doing a destroy on an instance the status,
    deleted, and deleted_at fields will still be the same as they were
    before, leaving the instance in an inconsistent state.

    This is important because our workers decorator for the HA A-A cleanup
    mechanism relies on the status of the resources being properly updated
    by the operations.

    Change-Id: I4f15356931007e2ca725e477327c1ef67c7db487
    Closes-Bug: #1604347

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/cinder 9.0.0.0b3 development milestone.