Cannot update service status on host ... since it is not registered

asked 2016-04-25 14:11:06 -0600

Nogginboink gravatar image

I'm installing OpenStack Liberty on Ubuntu Server 14.04LTS. I currently have a controller node and a compute node up and running and I can launch instances on the compute node.

I am now trying to add a second compute node ("ospt02") to my platform. I've installed the requisite software and have copied nova.conf and neutron/plugins/ml2/linuxbridge_agent.ini from my first compute node to my second node. I have changed $my_ip in the nova.conf on the second node to match its IP address.

When I start nova-compute on the second node, the service starts, but nova service-list does not list my second compute node. In nova-compute, I see:

2016-04-25 13:45:01.731 3522 DEBUG [-] Starting green dispatch thread _init_events usr/lib/python2.7/dist-packages/nova/virt/libvirt/
2016-04-25 13:45:01.731 3522 DEBUG [-] Connecting to libvirt: qemu:///system _get_new_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/
2016-04-25 13:45:01.746 3522 INFO nova.virt.libvirt.driver [-] Connection event '1' reason 'None'
2016-04-25 13:45:01.761 3522 WARNING nova.virt.libvirt.driver [req-c12f2708-0565-4197-84a7-fb2294a5e7b7 - - - - -] Cannot update service status on host "oscpt02" since it is not registered.
2016-04-25 13:45:01.762 3522 DEBUG [req-c12f2708-0565-4197-84a7-fb2294a5e7b7 - - - - -] Registering for lifecycle events < object at 0x7f9ff69639d0> _get_new_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/
2016-04-25 13:45:01.764 3522 DEBUG [req-c12f2708-0565-4197-84a7-fb2294a5e7b7 - - - - -] Registering for connection events: < object at 0x7f9ff69639d0> _get_new_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/
2016-04-25 13:45:01.782 3522 INFO [req-c12f2708-0565-4197-84a7-fb2294a5e7b7 - - - - -] Libvirt host capabilities <capabilities>

      <topology sockets='1' cores='8' threads='2'/>

The relevant line appears to be: WARNING nova.virt.libvirt.driver [req-c12f2708-0565-4197-84a7-fb2294a5e7b7 - - - - -] Cannot update service status on host "oscpt02" since it is not registered.

Both compute nodes can ping the controller node by name, and the controller node can ping both compute nodes by name. I can do an openstack token issue from my second compute node and can do a nova service-list from my second compute node (after copying the file from the first compute node and sourceing its contents) and I get a token issued or a list of nova services that does not include my second node.

Does anyone have any ideas on how I can get my second compute node to join its family?


edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-04-26 06:42:46 -0600

elenhil gravatar image

updated 2016-04-26 06:43:09 -0600


please verify that nova-conductor and nova-compute do have the same versions

i got the same error when i got conductor of version2:12.0.1-0ubuntu1~cloud0 and nova-compute 2:12.0.2-0ubuntu1~cloud0

to check it type

dpkg -l |grep nova

after conductor upgrade i got everything working

edit flag offensive delete link more


Well, Glory Be! That worked!

I never would have found that on my own... a thousand thanks!

Nogginboink gravatar imageNogginboink ( 2016-04-27 13:45:46 -0600 )edit

had the same problem with rdo: controller had openstack-nova-conductor-12.0.1-1.el7.noarch whilst new compute installs were using openstack-nova-compute-12.0.4-1.el7.noarch. just updated the controller and restarted the service and voila! all good again :)

yee379 gravatar imageyee379 ( 2016-06-22 00:57:57 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2016-04-25 14:11:06 -0600

Seen: 2,189 times

Last updated: Apr 26 '16