Ask Your Question
0

Unable to create instances on fresh Havana install [closed]

asked 2013-11-27 15:44:25 -0500

Jason T gravatar image

updated 2013-11-27 16:52:03 -0500

fifieldt gravatar image

Hi all,

I've got to this point in a fresh Havana install : http://docs.openstack.org/havana/install-guide/install/apt/content/nova-boot.html

The problem I've got is that on the compute node I just get an ERROR state after trying to startup an instance. created via : nova boot --flavor 1 --key_name mykey --image 8195e32e-cbdc-4812-a22a-14b73c7cdf82 --security_group default teststuff4

The error I'm getting when I do a nova show is : | fault | {u'message': u'No valid host was found. ', u'code': 500, u'details': u' File "/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py", line 107, in schedule_run_instance | | | raise exception.NoValidHost(reason="") | | | ', u'created': u'2013-11-27T21:25:52Z'}

Ahhhhaaa - So no compute host was found. So, turning to one of the two compute nodes (they're both setup the same and exhibiting the same issue) Looking at the compute node, nova-compute is starting but then bombing pretty much straight away. ala :

root@cloud-06:/var/log/nova# service nova-compute restart stop: Unknown instance: nova-compute start/running, process 3625 root@cloud-06:/var/log/nova# cat nova-compute.log

2013-11-27 21:31:17.023 INFO nova.openstack.common.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2013-11-27 21:31:17.064 INFO nova.virt.driver [-] Loading compute driver 'libvirt.LibvirtDriver'
2013-11-27 21:31:17.212 INFO nova.openstack.common.rpc.common [req-eb82da02-aba4-48fd-8ddb-1409305680f9 None None] Connected to AMQP server on 10.10.20.7:5672
2013-11-27 21:31:17.236 INFO nova.openstack.common.rpc.common [req-eb82da02-aba4-48fd-8ddb-1409305680f9 None None] Connected to AMQP server on 10.10.20.7:5672
2013-11-27 21:31:17.294 AUDIT nova.service [-] Starting compute node (version 2014.1)
2013-11-27 21:31:17.335 WARNING nova.virt.libvirt.driver [req-2d0804ca-d613-41dc-a5a6-75d705f00be9 None None] Cannot update service status on host: cloud-06,due to an unexpected exception.
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver Traceback (most recent call last):
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver   File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2669, in set_host_enabled
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver     service = service_obj.Service.get_by_compute_host(ctx, CONF.host)
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver   File "/opt/stack/nova/nova/objects/base.py", line 110, in wrapper
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver     args, kwargs)
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver   File "/opt/stack/nova/nova/conductor/rpcapi.py", line 469, in object_class_action
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver     objver=objver, args=args, kwargs=kwargs)
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver   File "/opt/stack/nova/nova/rpcclient.py", line 85, in call
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver     return self._invoke(self.proxy.call, ctxt, method, **kwargs)
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver   File "/opt/stack/nova/nova/rpcclient.py", line 63, in _invoke
2013-11-27 21:31:17.335 TRACE nova.virt.libvirt.driver     return cast_or_call(ctxt, msg ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason too localized by dheeru
close date 2013-12-05 08:18:49.612273

3 answers

Sort by ยป oldest newest most voted
1

answered 2013-11-28 11:44:34 -0500

dheeru gravatar image
After my deep code search I suspect you could be hitting this bug. Installing the patch may fix your issue. 

https://bugs.launchpad.net/nova/+bug/1239709

source code line 227 gave me a clue.
 @https://github.com/openstack/nova/blob/master/nova/objects/base.py 

objname = primitive['nova_object.name']
objver = primitive['nova_object.version']
objdata = primitive['nova_object.data']
objclass = cls.obj_class_from_name(objname, objver)
edit flag offensive delete link more
0

answered 2013-12-05 05:49:35 -0500

Jason T gravatar image

Well, We did a fresh install and followed the docs to the letter. This time it works in that we're not getting the error above, so I'd consider the issue closed. (we have other problems with the install now, but they'll be addressed 1 by 1) However, for people banging their head against a brick wall, I'd suggest a reinstall - of the compute node only, not the whole shebang. Not an ideal situation, but given that Openstack seems to have four different lines of documentation, and much of it is incoherent and disjointed, it'll have to do. I'd still consider Havana as not being production ready, but a good beta programme at the moment. Loads more on the documentation still to work on I think.

edit flag offensive delete link more
0

answered 2013-11-28 07:36:57 -0500

iTone gravatar image

Hi Is virtualisation enabled on the host processor of your compute nodes? I forgot to enable this in the bios when I first deployed openstack and got a similar error.

edit flag offensive delete link more

Comments

Hi there, Yes it is. I can run a VM manually in QEMU and KVM using virsh. It's just nova-compute that bombs as soon as it starts with : *IncompatibleObjectVersion_Remote: Version 1.2 of Service is not supported* as the principal error.

Jason T gravatar imageJason T ( 2013-11-28 10:59:07 -0500 )edit

Hi Jason, Have you managed to sort this one? I`m having IncompatibleObjectVersion error as well. Cheers, NM

azpekt gravatar imageazpekt ( 2014-02-03 02:43:53 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-11-27 15:44:25 -0500

Seen: 1,553 times

Last updated: Dec 05 '13