additional deployed compute nodes does not appear in nova

[lieni]

Mos 8.0, 3 node HA, VXLAN, Netapp plugin

We deployed a initial environment with 3 controllers an 2 compute nodes.
Deployment successfull.

We than added a new compute node.
The deployment of the node was successfully.
But the node does not appear in nova (nova host-list oder service-list)
Neutron Services are published an available in dashboard.

Error on compute node is:
nova.virt.libvirt.driver [req-a8f57258-0900-42c9-8809-c2ed5a3945f8 - - - - -] Cannot update service status on host "smc2-2" since it is not registered.

Is this a bug or somthing went wrong?
We allready deleted the node and redeployed it, same results.
We got some more compute nodes tomorrow, we will thest to add this ones.

Thank you

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[lieni (oliver-lienhard-b)]

I found following on https://ask.openstack.org/en/question/91496/cannot-update-service-status-on-host-since-it-is-not-registered/

error is while following packages are other versions:
conductor 2:12.0.0-1 u14.04+mos43
nova-compute 2:12.0.2-1 u14.04+mos21
someone reportrd, after upgrade conductor on controlles, compute node aperars in nova.

so should we run abt-get upgrade on all nodes for all patches?
Or only for conductor?
It is a produtive environment?

Thank you for your advice

[Roman Podoliaka (rpodolyaka)]

Could you please attach a diagnostic snapshot? Or at least provide a full /var/log/nova/nova-compute.log from the compute node in question? (try to restart the nova-compute service on the affected node first - service nova-compute restart)

[lieni (oliver-lienhard-b)]

Hi
we allready restartet all nova services as well the node itself.
We test to downgrade the nova-compute package on this host, becaus on the other 2 compute nodes that worked the package-version is:

nova-compute 2:12.0.0-1~u14.04+mos43
the new deployed host that was unable to register to nova has:
nova-compute 2:12.0.2-1 u14.04+mos21

In general, it is ok to to a abt-get upgrade on nodes?
Because there are a lot of warningings on all services in the logs about depercated soon conf-settings. Not that we break the running system?

Some Nova Compute Log.
2016-05-17 14:17:47 WARNING nova.virt.libvirt.driver [req-d21e0fbf-8cfe-4938-8f43-5d30bb48254b - - - - -] Cannot update service status on host "smc2-2.domain.tld" since it is not registered.
2016-05-17 14:17:47 INFO nova.virt.libvirt.driver [-] Connection event '1' reason 'None'
2016-05-17 14:17:47 INFO nova.service [-] Starting compute node (version 12.0.2)
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "lock_path" from group "DEFAULT" is deprecated. Use option "lock_path" from group "oslo_concurrency".
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "vncserver_proxyclient_address" from group "DEFAULT" is deprecated. Use option "vncserver_proxyclient_address" from group "vnc".
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "vncserver_listen" from group "DEFAULT" is deprecated. Use option "vncserver_listen" from group "vnc".
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "novncproxy_base_url" from group "DEFAULT" is deprecated. Use option "novncproxy_base_url" from group "vnc".
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "vnc_keymap" from group "DEFAULT" is deprecated. Use option "keymap" from group "vnc".
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "vnc_enabled" from group "DEFAULT" is deprecated. Use option "enabled" from group "vnc".
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "auth_strategy" from group "neutron" is deprecated for removal. Its value may be silently ignored in the future.
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "admin_username" from group "neutron" is deprecated for removal. Its value may be silently ignored in the future.
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "admin_tenant_name" from group "neutron" is deprecated for removal. Its value may be silently ignored in the future.
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "admin_password" from group "neutron" is deprecated for removal. Its value may be silently ignored in the future.
2016-05-17 14:17:46 WARNING oslo_config.cfg [req-94e7bbb0-e221-404f-907d-65c90ef6b2b3 - - - - -] Option "admin_auth_url" from group "neutron" is ...

[Denis Meltsaykin (dmeltsaykin)]

I'm marking this report as a duplicate of bug#1592118. You can find solution in the https://bugs.launchpad.net/fuel/+bug/1592118