**cinder_cert.sh**, wrapper around the tempest volume api tests, doesn't restart Cinder services correctly

[Andrii Bondar]

here is the trace:

$ ./cinder_driver_cert.sh
...
========================================================
08/29/14/12:07:58:Restart Cinder services...,
========================================================
tgt stop/waiting
stop: Unknown instance:
tgt start/running, process 17653
Waiting for Cinder API to start...
timeout: invalid time interval `http://172.18.198.94:8776'
Try `timeout --help' for more information.
[Call Trace]
./cinder_driver_cert.sh:92:start_cinder
/home/stack/jenkins/workspace/Coraid_CI/devstack/lib/cinder:438:die
[ERROR] /home/stack/jenkins/workspace/Coraid_CI/devstack/lib/cinder:438 c-api did not start
...

I fixed this issue by exporting $SERVICE_TIMEOUT variable to user environment:

export SERVICE_TIMEOUT=${SERVICE_TIMEOUT:-60}

[Dean Troyer (dtroyer)]

Fix: Add the definition of SERVICE_TIMEOUT to driver_certs/cinder_driver_cert.sh

[Sean Dague (sdague)]

This 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.