[Openstack] cinder create error
b t
905ben at gmail.com
Tue Sep 23 04:45:58 UTC 2014
thank you guys , my first instance is up and running .
the issue is compute node .
first thing to fix is to enable qemu because its nested vm.
solution is to modify nova-compute.conf
virt_type=qemu
and apt-get install nova-compute-qemu
second things is to fix this error message :
VirtualInterfaceCreateException: Virtual Interface creation failed
the solution is to add the following in nova.conf [default]
vif_plugging_timeout = 10
vif_plugging_is_fatal = False
On Sat, Sep 20, 2014 at 2:07 AM, Radek Smigielski <
radek.smigielski at ymail.com> wrote:
>
> >>>> root at controller:/var/log/cinder# more cinder-scheduler.log
> >>>> 2014-09-12 22:47:41.757 10328 ERROR
> cinder.scheduler.flows.create_volume
> [req-5c268fcf-5c4d-49ed-be1b-0460411e76b0 33444db757c14559add65a2e606c2102
> d4c3bf6ee2af44129fc38bf76f4a5623 - - -] Failed
> >>>> to schedule_create_volume: No valid host was found.
> >>>> 2014-09-12 22:56:01.742 10328 WARNING cinder.context [-] Arguments
> dropped when creating context: {'user':
> u'dfbdec26a06a4c5cb35f994937b092fb', 'tenant':
> u'0faf8d7dfdac4a53af195b5436992976', 'use
> >>>> r_identity': u'dfbdec26a06a4c5cb35f994937b092fb
> 0faf8d7dfdac4a53af195b5436992976 - - -'}
> >>>> 2014-09-12 22:56:01.765 10328 ERROR
> cinder.scheduler.flows.create_volume
> [req-230d0a9c-851c-4612-9549-cc9fb07a2197 dfbdec26a06a4c5cb35f994937b092fb
> 0faf8d7dfdac4a53af195b5436992976 - - -] Failed
> >>>> to schedule_create_volume: No valid host was found.
> >>>> root at controller:/var/log/cinder#
>
> IMHO, tke key to resolve this problem is to look back on
> cinder-scheduler.log where you see this error:
>
>
> >> Failed to schedule_create_volume: No valid host was found.
>
> Also looking on your cinder.conf, you seem to be using LVM over iSCSI as a
> storage, is that correct?
> "No valid host was found" probably means some cinder or iSCSI
> misconfiguration, ie:
>
>
>
> 1.I don't see any LVM filters in your config so schedululer may be confised
> 2. double check if your hosts really have woorking iSCSI access to your
> storage? this is often source of many problems
>
>
> Cheers,
> Radek.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140923/4f1a68a8/attachment.html>
More information about the Openstack
mailing list