Comment 24 for bug 1323658

I investigated this problem based on the latest failure http://logs.openstack.org/59/120159/1/gate/gate-tempest-dsvm-neutron/be422ac/ , and Tempest could not get server console-log[1] again as Kyle at comment #21.
In this case, the scheduling a sever started 18:57:10 and the server became Active 18:57:21.

According to nova-cpu log, a server creation seems successful with the message "Instance spawned successfully."
and there is nothing special on both libvirtd.txt.gz and kern_log.txt.gz in the above period.
I guessed this problem was a server creation failure but I could not find its evidence and the reason why we are
facing this problem on Neutron gate.

[1]: https://github.com/openstack/tempest/blob/master/tempest/scenario/manager.py#L705