Comment 15 for bug 1374175

The error message mentioned occurs during a different test, so it's not related.

This test works by waiting for the server resource to move to CREATE_COMPLETE (this part seems to be working), then starts pinging the server with a timeout of CONF.compute.ping_timeout (120s by default). That's the part that's failing - Tempest can't ping the server within 2 minutes of Nova reporting that it's running.

As Steve said, that could be a connectivity problem or a simple case of booting the server taking slightly too long (or it could be a problem with the image being booted). It doesn't seem like a problem that Heat itself could cause, since it's not involved here beyond reporting success from Nova.