Comment 2 for bug 1606551

I've checked the logs and see that scheduling failed because there were no compute nodes available:

http://paste.openstack.org/show/549211/

^ ComputeFilter failed, which basically means we haven't heard from the compute node (we only have one in this environment) for a while. Are you sure you are giving the node enough time to return back online after reboot?

It looks like you do not:

http://paste.openstack.org/show/549213/

^ the nova-compute process just started when the scheduling request failed.

IMO, we should change the test case to wait until the corresponding nova-compute process is marked `up` again in the `nova service-list` output after reboot of the node.