Tripleo CI Fails to get a Test Env in a timely manner

[Derek Higgins]

This is a placeholder bug for rechecks linked with problems getting a test env .

Tripleo CI tests can fail if they fail to get a test environment (or are delayed getting one)

This can occur if
  o There is a shortage of operating Test Envs
  o There is a problem with communication with geard

This is identified by a long delay after this line in the console log

2014-05-29 13:39:52.554 | + ./testenv-client -b 192.168.1.1:4730 -t 7200 -- ./toci_devtest.sh

followed by a jenkins timeout on the overall job (there may be log entries in between if the job did eventually get a testenv)
2014-05-29 15:40:41.887 | Build timed out (after 125 minutes). Marking the build as failed.

during normal operations the log entry after the call to "testenv-client" should be within a second but we can tolerate a delay of over an hour (depending on the job type)