Nova Compute Node not starting properly

asked 2018-04-16 07:51:01 -0600

Arjun
1 ●3 ●4 ●4

updated 2018-04-17 03:37:16 -0600

After installing Nova Compute Node using the Installation Tutorial from Queens Repository https://docs.openstack.org/nova/queens/install/compute-install-ubuntu.html#install-and-configure-components (https://docs.openstack.org/nova/queen...)

Getting the Following Error Message when tried to start the Nova Compute Node

# service nova-compute restart

These are the Error Message from the /var/log/nova/nova-compute.log

2018-04-16 18:13:34.549 22865 WARNING nova.scheduler.client.report [req-094894bb-c711-4e00-8733-f4a0fcf9df3c - - - - -] Placement API service is not responding.: ConnectFailure: Unable to establish connection to http://controller:35357/v3/auth/tokens: HTTPConnectionPool(host='controller', port=35357): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f47500302d0>: Failed to establish a new connection: [Errno 111] ECONNREFUSED',))
2018-04-16 18:13:34.551 22865 WARNING nova.scheduler.client.report [req-094894bb-c711-4e00-8733-f4a0fcf9df3c - - - - -] Placement API service is not responding.: ConnectFailure: Unable to establish connection to http://controller:35357/v3/auth/tokens: HTTPConnectionPool(host='controller', port=35357): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f4750030910>: Failed to establish a new connection: [Errno 111] ECONNREFUSED',))
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager [req-094894bb-c711-4e00-8733-f4a0fcf9df3c - - - - -] Error updating resources for node UbuntuVM4.: TypeError: 'NoneType' object has no attribute '__getitem__'
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager Traceback (most recent call last):
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 7254, in update_available_resource_for_node
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager     rt.update_available_resource(context, nodename)
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 680, in update_available_resource
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager     self._update_available_resource(context, resources)
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager   File "/usr/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py", line 277, in inner
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager     return f(*args, **kwargs)
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 704, in _update_available_resource
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager     self._init_compute_node(context, resources)
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 561, in _init_compute_node
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager     self._update(context, cn)
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 878, in _update
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager     inv_data,
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/__init__.py", line 68, in set_inventory_for_provider
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager     parent_provider_uuid=parent_provider_uuid,
2018-04-16 18:13:34.551 22865 ERROR nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/__init__.py", line ...

(more)

edit retag flag offensive close merge delete

add a comment

2 answers

Sort by » oldest newest most voted

answered 2018-04-16 09:22:58 -0600

Bernd Bausch

6224 ●40 ●74 ●145 https://www.linkedin.c...

updated 2018-04-16 18:57:38 -0600

The compute node seems to be unable to access Keystone at http://controller:35357/v3/auth/tokens. ECONNREFUSED indicates that the controller does not block port 35357, but no process is listening at that port on the controller. Most likely Keystone is not running.

Thus, the next step is checking if Keystone is running on the controller, and if not, why. The Keystone log is the first place to check.

If it is running, use curl to access that URL from the compute node and try to figure out where the Connection Refused error comes from.

Another possibility is that http://controller is not what you think. Perhaps the compute node configures an incorrect IP address for the controller.

Since nova-compute can't authenticate, it can't access the Placement API.

"TypeError: 'NoneType' object has no attribute '__getitem__'", looks like a bug or a mismatch between the versions of two Nova components. Perhaps it's a consequence of the other errors, perhaps it's a bug in the error handling code. I would first fix the Keystone access problem; the other errors might go away then.

Etcd, MySQL, MemCache, RabbitMQ are normally installed on controllers, not on compute nodes.

edit flag offensive delete link

Comments

Hello Bernd Bausch, I checked. Keystone is running on Controller Node. It is configured for listening on both 5000 and 35357 ports. I have configured controller node address in compute node in both /etc/hosts and as well as nova.conf files. Will try to run curl.

Arjun ( 2018-04-16 21:47:05 -0600 )edit

add a comment

answered 2018-04-17 03:36:38 -0600

Arjun
1 ●3 ●4 ●4

KeyStone is running on the Controller Node. Port it is listening is on Port 5000 and it is not listening on 35357 port. From the Nova Compute Node, I am able to curl to the controller node with the 5000 port.

curl -v http://controller:5000/v3 SUCCESS

curl -v http://controller:35357/v3 CONNECTION FAILED.

Is there any way to make KeyStone Listen on Port 35357 on the Controller Node.

I have followed the Instructions exactly as given in the Installation Tutorial.

edit flag offensive delete link

Comments

Could be doc bug. Instructions seem to only configure port 5000 for Keystone, but auth_url = http://controller:35357 on the the compute node. Try setting auth_url = http://controller:5000 instead.

Bernd Bausch ( 2018-04-17 06:09:54 -0600 )edit

Or start from scratch again and configure Keystone the Pike way, i.e. step 5 on https://docs.openstack.org/keystone/p....

Bernd Bausch ( 2018-04-17 06:12:51 -0600 )edit

Got the Problem Fixed. Change the Repository from Queens to Pike. So, the Port Numbers are changed from 5000 to 35357. Now, the Controller Node is listening on both 5000 and 35357 ports as well. Compute Node of Nova works fine. Thanks Mr. Bernd Bausch for your feedback.

Arjun ( 2018-04-18 11:01:44 -0600 )edit

add a comment

Nova Compute Node not starting properly

2 answers

Comments

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Nova Compute Node not starting properly edit

2 answers

Comments

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Nova Compute Node not starting properly