no valid host was found in multinode setup
While creating a VM on a multinode OpenStack setup I am getting the following error:
"message": "No valid host was found. ", "code": 500, "details": " File \"/usr/lib/python2.7/dist-packages/nova/conductor/manager.py\", line 616, in build_instances
I have a multinode setup with a Compute node, Controller node and a network node. While running "nova service-list" command all my services are up and enabled. So I am not getting where are we going wrong in regards to this.
logs of nova.conductor.log
c20b69a2-0441-4a16-b14a-68f15b93b862 None] [instance: 2d631bcc-fdd1-4bba-ae46-9bc2dfff8963] Error from last host: compute (node compute): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2036, in _do_build_and_run_instance\n filter_properties)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2167, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance 2d631bcc-fdd1-4bba-ae46-9bc2dfff8963 was re-scheduled: Unexpected vif_type=binding_failed\n'] 2015-05-01 12:42:27.879 5183 WARNING nova.scheduler.driver [req-c20b69a2-0441-4a16-b14a-68f15b93b862 None] [instance: 2d631bcc-fdd1-4bba-ae46-9bc2dfff8963] NoValidHost exception with message: 'No valid host was found.' 2015-05-01 12:42:27.879 5183 WARNING nova.scheduler.driver [req-c20b69a2-0441-4a16-b14a-68f15b93b862 None] [instance: 2d631bcc-fdd1-4bba-ae46-9bc2dfff8963] Setting instance to ERROR state.
Can you verify your filter parameter in your configuration file?
i did not get you. can you please explain, how to verify filter parameter.
Filter values are defined using scheduler_default_filters parameter in nova.conf. Can you post the values?
i checked nova.conf file in both compute and controller node there we did not defined any scheduler_default_filters.
I changed scheduler_default_filters in both controller or compute node and restarted the nova servicesand booted a vm but that vm went to scheduling state and not coming in running state. Is there specific node we have to change scheduler_default_filters value ?