Caching the client can cause the int-tests to fail on slow nodes

[Peter Stachowski]

If a node is really slow then a single test can take longer than an hour. It will then fail as client it has cached will now have an expired token. To alleviate this, the caching of the clients should be removed (since the time saved on caching the clients is probably negligible anyway).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/406503
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=d558e5c2e0b02a9f3f52e1370bdfe5b1495a4b31
Submitter: Jenkins
Branch: master

commit d558e5c2e0b02a9f3f52e1370bdfe5b1495a4b31
Author: Peter Stachowski <email address hidden>
Date: Sat Dec 3 18:25:19 2016 +0000

    Stop caching client to fix long-running test fails

    If a node is really slow then a single test can take longer than an
    hour. It will then fail as the client it has cached will now have an
    expired token. To alleviate this, the caching of the clients was removed
    (since the time saved on caching the clients is probably negligible
    anyway).

    Checking the client code was also cleaned up for a number of tests.

    The cluster tests were modified, however the code was reverted as
    there is no way to test it at present (they will not run as they
    haven't been modified to work with the new neutron set up). This
    will be fixed in a separate changereq (since they are currently not
    being tested in the gate, this should not hold up development).

    Change-Id: I63d5b78084486b806bff38068260e42128c0d0ed
    Closes-Bug: 1647002

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/trove 7.0.0.0b2 development milestone.