Comment 5 for bug 1486417

There are no errors /traces in heat/ceilometer logs which would point to any problems and lead to timeout errors. Problem also is not in cluster configuration.
My point is that:
1) 176 ISO is not stable by itself and maybe there are some problems with rabbit/connectivity/etc which can cause timeout issues:
--- this ISO was not tested on BVT jobs
--- results of SWARM job for this ISO is unstable
(here all tests were failed:
http://jenkins-product.srt.mirantis.net:8080/view/7.0_swarm/job/7.0.system_test.ubuntu.services_ha_one_controller/60/
and here all is ok:
http://jenkins-product.srt.mirantis.net:8080/view/7.0_swarm/job/7.0.system_test.ubuntu.services_ha_one_controller/61/)
2) FUEL environment is too slow (there is 2 Gb of RAM and 1 CPU on compute node), for example first test "Typical stack actions" failed because after stack was created test couldn't get/receive stack info during 20 sec (it is large timeout for such operation)

We can't increase timeout infinitely every time when tests fails in some slow/unstable environments.