This looks interesting. According to stack traces of green/native threads attached above nova-compute is in a weird state: eventlet main loop is started and fully functional, nova-compute is connected to rabbitmq/libvirt (libvirt keep alives go into both direction periodically), while at the same time looks like nova-compute RPC server has not started properly, so it does not really wait for any new messages, nor executes periodic tasks of its own.
This looks interesting. According to stack traces of green/native threads attached above nova-compute is in a weird state: eventlet main loop is started and fully functional, nova-compute is connected to rabbitmq/libvirt (libvirt keep alives go into both direction periodically), while at the same time looks like nova-compute RPC server has not started properly, so it does not really wait for any new messages, nor executes periodic tasks of its own.