Devstack exercise: Trove API not functioning!

[Dolph Mathews]

I encountered this as a transient failure in during the 'trove' exercise:

  http://logs.openstack.org/60/107560/3/gate/gate-devstack-dsvm-cells/d78c22d/console.html

Logs:

2014-07-22 01:09:02.498 | + curl http://127.0.0.1:8779/
2014-07-22 01:09:02.498 | + grep -q versions
2014-07-22 01:09:02.498 | + die 39 'Trove API not functioning!'
2014-07-22 01:09:02.499 | + local exitcode=1
2014-07-22 01:09:02.499 | + set +o xtrace
2014-07-22 01:09:02.499 | [Call Trace]
2014-07-22 01:09:02.499 | /opt/stack/new/devstack/exercises/trove.sh:39:die
2014-07-22 01:09:02.499 | [ERROR] /opt/stack/new/devstack/exercises/trove.sh:39 Trove API not functioning!

[Dolph Mathews (dolph)]

e-r query (currently 2 hits in 2 weeks): https://review.openstack.org/#/c/108575/

[Denis M. (dmakogon)]

Bug was repeated. But this is a bug for devstack, not for Trove, and i know how to fix it.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/108961
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=3e57427bf2596be7fd389d27c9f7c08c7a4a265f
Submitter: Jenkins
Branch: master

commit 3e57427bf2596be7fd389d27c9f7c08c7a4a265f
Author: Denis Makogon <email address hidden>
Date: Wed Jul 23 14:36:20 2014 +0300

    Fix exercises for Trove

    Reasons:
     - trove.sh should use native python client to exercise Trove API

    Changes:
     - adding datastore and datastore version exercises

    Change-Id: I041465e5bda6ad9ec3f597ecc290612b8baef09c
    Closes-Bug: #1346743

[Dolph Mathews (dolph)]

Re-opening, as this still has 8 failures in the last 24 hrs according to elastic-recheck (long after the above patch merged).

[Sean Dague (sdague)]

This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.