Nailgun start check (run_server in run_tests.sh) doesn't work properly

[Vitaly Kramskikh]

It happens on slow machines and/or in VMs. In this case there is just a message "Failed to start Nailgun".

To avoid this issue, I propose the following changes:

1) Increase number of check attempts from 10 to 30-50
2) Print explicit error message in case of timeout

[Vitaly Kramskikh (vkramskikh)]

It seems it is possible to control timeout by setting env var NAILGUN_START_MAX_WAIT_TIME, but explicit message is still needed

[Vitaly Kramskikh (vkramskikh)]

It seems this check doesn't work at all as it uses $NAILGUN_CHECK_URL which uses $NAILGUN_PORT instead of $UI_SERVER_PORT. So it always waits for 5s.

[Roman Prykhodchenko (romcheg)]

Vitaly, could you please describe, what information should be added to the message?

[Vitaly Kramskikh (vkramskikh)]

I think there should be a common message like "Nailgun didn't start in ${NAILGUN_START_MAX_WAIT_TIME}s. Use NAILGUN_START_MAX_WAIT_TIME var to increase timeout". In case of non-timeout failure there could be a path to log file

[Roman Prykhodchenko (romcheg)]

Thank's for your response. I'll publish a patch soon.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/175961
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=9d7e7247e44b1b73fe293f5b020a41fc70697a1d
Submitter: Jenkins
Branch: master

commit 9d7e7247e44b1b73fe293f5b020a41fc70697a1d
Author: Roman Prykhodchenko <email address hidden>
Date: Tue Apr 21 17:57:50 2015 +0200

    Refactored run_server script

    Used the updated version of run_server script
    from python-fuelclient.

    Closes-bug: #1446211
    Change-Id: I2c8538fa6e3854f2c33434a1b08d366121cc55b1