Ask Your Question
0

unable to launch instance on second compute node

asked 2014-05-23 07:24:48 -0500

sudarshan gravatar image

Hi,

i can see 2 compute nodes from horizon but launch instance doesnt create instance on the newly configured compute node. it creates in the old compute only. if i force create instance on cmpt1 from command line i get following error

nova-scheduler log

2014-05-23 13:47:34.037 19332 INFO nova.scheduler.filter_scheduler [req-0d0d6b02-b166-4591-a470-83088e78eef9 8aadb455a49f45b8b7f9c1805a4bdd6d 816a2f51284a417fabe52aa4dc602b04] Choosing host WeighedHost [host: heos-cmpt1, weight: 1.0] for instance c0d2b911-6d94-42a5-9d0f-aacb50bd64f8
2014-05-23 13:47:39.425 19332 INFO nova.scheduler.filter_scheduler [req-0d0d6b02-b166-4591-a470-83088e78eef9 8aadb455a49f45b8b7f9c1805a4bdd6d 816a2f51284a417fabe52aa4dc602b04] Attempting to build 1 instance(s) uuids: [u'c0d2b911-6d94-42a5-9d0f-aacb50bd64f8']
2014-05-23 13:47:39.427 19332 ERROR nova.scheduler.filter_scheduler [req-0d0d6b02-b166-4591-a470-83088e78eef9 8aadb455a49f45b8b7f9c1805a4bdd6d 816a2f51284a417fabe52aa4dc602b04] [instance: c0d2b911-6d94-42a5-9d0f-aacb50bd64f8] Error from last host: heos-cmpt1 (node heos-cmpt1.cisco.com): [u'Traceback (most recent call last):\n', u'  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1311, in _build_instance\n    set_access_ip=set_access_ip)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 399, in decorated_function\n    return function(self, context, *args, **kwargs)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1723, in _spawn\n    LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68, in __exit__\n    six.reraise(self.type_, self.value, self.tb)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1720, in _spawn\n    block_device_info)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2253, in spawn\n    block_device_info)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3644, in _create_domain_and_network\n    power_on=power_on)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3547, in _create_domain\n    domain.XMLDesc(0))\n', u'  File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68, in __exit__\n    six.reraise(self.type_, self.value, self.tb)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3542, in _create_domain\n    domain.createWithFlags(launch_flags)\n', u'  File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 179, in doit\n    result = proxy_call(self._autowrap, f, *args, **kwargs)\n', u'  File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 139, in proxy_call\n    rv = execute(f,*args,**kwargs)\n', u'  File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 77, in tworker\n    rv = meth(*args,**kwargs)\n', u'  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 896, in createWithFlags\n    if ret == -1: raise libvirtError (\'virDomainCreateWithFlags() failed\', dom=self)\n', u"libvirtError: Unable to pre-create chardev file '/var/lib/nova/instances/c0d2b911-6d94-42a5-9d0f-aacb50bd64f8/console.log': Permission denied\n"]
edit retag flag offensive close merge delete

Comments

Does your Nova scheduler find enough resources in first compute node so that it doesn't consider second compute node?

SGPJ gravatar imageSGPJ ( 2014-05-23 13:07:06 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-05-24 16:34:21 -0500

craigtracey gravatar image

From the looks of the logs, this is due to a nova-compute failure to create the instance on the remote compute host. And, further, it looks like the issue is that the user running the nova service is unable to write to /var/lib/nova. I would check permissions there first - they are almost certainly incorrect and the root cause of this issue.

Secondarily, be sure to check that the nova services are in a good state. "nova service-list" will show you what the state of each nova service is throughout the cluster. While it would not show this runtime failure, it may alert you to other issues.

Hope this helps, Craig

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

Stats

Asked: 2014-05-23 07:24:48 -0500

Seen: 1,051 times

Last updated: May 24 '14