Comment 11 for bug 1374175

There are quite a few (non Heat) reasons why this could be happening:

1. Network fault meaning we can't connect to the instance
2. Instance is booting but slowly, so the timeout expires before the WaitCondition completes.

All the test does is boot an instance (via heat), then fail when trying to ping it due to exceeding
CONF.compute.ping_timeout (default is 120s).

It's possible 120s is not enough time to boot a Fedora image and/or some new (slower) compute nodes were added to the gate infra recently?