I have a multi-node set up with 2 compute nodes( Compute1 and Compute2). When I boot VM's on compute 1 they go to ACTIVE status but when I try to boot VM's on Compute2 host they are stuck in BUILD status. I can see both the compute nodes UP in “nova service-list” and both the host are present in “nova hypervisor-list” So what could be the reason that VM's are not going to ACTIVE status in Compute2 host.

I can see this error in the nova scheduler logs (/var/log/nova/nova-scheduler.log)

2015-05-20 10:01:44.450 9564 TRACE nova.servicegroup.drivers.db OperationalError: (OperationalError) database is locked u'UPDATE services SET updated_at=?, report_count=? WHERE services.id = ?' ('2015-05-20 04:31:44.431308', 41861, 2) 2015-05-20 10:01:44.450 9564 TRACE nova.servicegroup.drivers.db 2015-05-20 10:01:54.440 9564 ERROR nova.servicegroup.drivers.db [-] Recovered model server connection! 2015-05-20 10:44:11.649 9564 AUDIT nova.scheduler.host_manager [req-481421a9-c29b-4fe1-adf1-c07b0e01e556 None] Host filter forcing available hosts to compute1 2015-05-20 10:46:08.646 9564 AUDIT nova.scheduler.host_manager [req-b5a482d3-6aab-40a2-8b11-fb4fca888870 None] Host filter forcing available hosts to compute 2015-05-20 10:50:10.035 9564 AUDIT nova.scheduler.host_manager [req-a4debdff-0ad5-4fb8-afd4-e0dc255c3c78 None] Host filter forcing available hosts to compute1