[ostf] OSTF test "Create volume and boot instance from it" fail by timeout

[Anastasia Palkina]

"build_id": "2014-06-16_00-31-15",
"mirantis": "yes",
"build_number": "255",
"ostf_sha": "67b61ed3788297fa5d985afec32498d8c0f812db",
"nailgun_sha": "984aa7a86487f1488c2f83c052904abd9f589b7f",
"production": "docker",
"api": "1.0",
"fuelmain_sha": "6f355160366475d52050d7898a1080a95ecb9cbf",
"astute_sha": "17b1afa5f0dc8f4fca5ed4eb03ec566fbfb5ed19",
"release": "5.1",
"fuellib_sha": "99d74172887ab81d38132655d6e5d180e8726437"

1. Create new environment (Ubuntu, HA mode)
2. Choose VLAN segmentation
3. Choose both Ceph
4. Choose Murano installation
5. Add 3 controllers, compute, 3 ceph
6. Start deployment. It was successful
7. Start OSTF tests
8. Test "Create volume and boot instance from it" has failed on step 2 with error: Timed out waiting to become available Please refer to OpenStack logs for more details.
9. Login to Horizon
10. Move to Project -> Compute -> Volumes
11. I ran this OSTF test 2 times and 2 bootable volumes are available and they was not deleted (see screen)

So we have two problems:
a) lack of timeout;
b) volumes was not deleted.

[Tatyanka (tatyana-leontovich)]

Vulume stay in downloading status more then 300 secind. As result test interrupt by timeout. Deletion fail - according we can not delete volume in downloading state
We can set timeout bigger, BUT we should understand why the volume talkes so much the time to be available(we should measure this invocation may we with strace)

[Dmitry Pyzhov (dpyzhov)]

Looks like local performance issue. We can try address it with blueprint https://blueprints.launchpad.net/fuel/+spec/ostf-dynamic-timeouts