DSVM jobs are broken on stable/liberty

[Goutham Pacha Ravi]

manila's CI hooks checkout a particular version of tempest on stable/liberty. Tempest recently introduced a new tox change:
 https://github.com/openstack/tempest/commit/0e25a90793a17728ab235d21ee282db31add3d74

The change introduced a new "venv-tempest" tox configuration. The stable/liberty version of devstack was updated recently to expect this venv:
 https://github.com/openstack-dev/devstack/commit/525bc5cfe4d67cda3e93a0eaf7560b524804484a

As expected, us 'pinning' a particular version of tempest is breaking our CI runs on stable/liberty:
 https://github.com/openstack/manila/blob/stable/liberty/contrib/ci/pre_test_hook.sh#L69

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/342472
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=bf791c45e3daedc604eb16be12d28721c56f4084
Submitter: Jenkins
Branch: stable/liberty

commit bf791c45e3daedc604eb16be12d28721c56f4084
Author: Goutham Pacha Ravi <email address hidden>
Date: Thu Jul 14 19:51:15 2016 -0400

    [CI Fix] Hotfix for stable/liberty jobs

    Tempest is branchless, but highly tempestuous in itself.
    We have had many breakages in the manila stable branch jobs
    because of changes made to the clients that we use for tempest.
    This led us to pin a particular commit of tempest. However, when
    the changes made to tempest are taken to stable branches of
    devstack in any form [1], our stable branch jobs are no longer
    protected by the 'stable' commit that we checkout. Without
    bringing in the horde of changes to our stable branch, we could
    cherry-pick the offending tempest change [2] on top of the
    existing 'stable' commit.

    [1] I63658b8d8dfa999e0feb79f8f2968f2b32e3ff57
    [2] Iab2e6e04b6c5795a4d0c8214564106525b942308

    Closes-Bug: #1603275

    Change-Id: I4248c704256fc790082f3ac2515c6445ac7aa78a

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/manila 1.0.2 release.