Ask Your Question

nova-scheduler fails (no report updates), nova network-create not working

asked 2014-09-03 10:22:50 -0600

jsubirat gravatar image

updated 2014-09-04 08:31:19 -0600

My OpenStack installation was working just fine but I was experiencing the problems described in: (

I tried to manually change the permissions of the files in /var/lib/nova (mounted as a NFS share, working fine until now), and I dropped and recreated the nova database with the following commands (DO NOT USE THEM!):


service nova-api stop && service nova-cert stop && service nova-consoleauth stop && service nova-scheduler stop && service nova-conductor stop && service nova-novncproxy stop

mysql --user="$user" --password="$password" --execute="DROP DATABASE nova; CREATE DATABASE nova; GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'localhost' IDENTIFIED BY '$passwordnova'; GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'%' IDENTIFIED BY '$passwordnova';"

nova-manage db sync

When I restarted all the services in the controller node, I observed that the nova-compute services were not being reported anymore, and the nova-scheduler was reported as:

Binary           Host                                 Zone             Status     State Updated_At
nova-network     compute0                            internal         enabled    :-)   2014-09-03 14:38:49
nova-consoleauth controller                          internal         enabled    :-)   2014-09-03 14:38:50
nova-cert        controller                          internal         enabled    :-)   2014-09-03 14:38:50
nova-conductor   controller                          internal         enabled    :-)   2014-09-03 14:38:50
nova-scheduler   controller                          internal         enabled    XXX   None      
nova-network     compute1                            internal         enabled    :-)   2014-09-03 14:38:53

I checked the keystone database, and the report_count of nova-scheduler in the table is 0. Therefore, it looks like the nova-scheduler is not working properly. I've checked it's log (/var/log/nova/nova-scheduler.log), and it simply says:

2014-09-03 14:47:07.309 17835 AUDIT nova.service [-] Starting scheduler node (version 2013.1)
2014-09-03 14:47:08.252 INFO nova.openstack.common.rpc.common [req-484eed9e-0266-414d-aed9-5d34a19197fa None None] Connected to AMQP server on controller:5672
2014-09-03 14:47:08.315 INFO nova.openstack.common.rpc.common [req-484eed9e-0266-414d-aed9-5d34a19197fa None None] Connected to AMQP server on controller:5672

Given that I silly deleted the nova database, I also lost the previously created network (a flat one). So, I tried to recreate it with:

nova network-create vmnet --fixed-range-v4= --bridge=br100 --multi-host=T

But this command is hung forever. So, I executed it with --debug and I obtained:

I've reinstalled the packages but to no avail. Do you have an idea of what might be wrong? Many thanks!

EDIT: I deleted all the databases, purged all the OpenStack packages in the controller node, and started over again from the beginning, following the Havana tutorial. But when I get to the nova network-create step in: (

It timeouts. Any idea? Thanks!

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-09-04 09:26:24 -0600

SlOPS gravatar image

Check service nova-scheduler status. It may fails without messages.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-09-03 10:22:50 -0600

Seen: 181 times

Last updated: Sep 04 '14