Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes

2017-02-20 Thread Kevin Benton 
Expanding on that, you get that binding error usually when Neutron thinks
it can't wire up the ports on the compute nodes. So ensure that you started
the appropriate Neutron agents on the new compute nodes and that they are
alive by running 'neutron agent-list'.

On Mon, Feb 20, 2017 at 8:14 AM, Kostyantyn Volenbovskyi <
volenbov...@yandex.ru> wrote:

> Hi,
> this 'Unexpected vif_type=binding_failed’ is as well fairly-generic, but
> you can change focus from Nova to Neutron+virtual switch.
>
> So check:
> -Neutron server logs
> -Logs of Neutron agent on target Compute Host(s)
> -OVS logs and possibly things like /var/log/messages for things related to
> virtual networking.
>
> The root cause is typically:
> -misconfiguration of mechanism driver/type driver.
> -misconfiguration of virtual switching (typically OVS)
> Go through installation documents in docs.openstack.org, that provides a
> guide for values
> parameters related to that.
>
>
> BR,
> Konstantin
>
> On Feb 20, 2017, at 8:16 AM, Anwar Durrani 
> wrote:
>
> Further when i tried and attempt to launch new instance, i can see the
> following
>
> tail -f /var/log/nova/nova-compute.log
>
>
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
> 1840ac2e-5a54-4941-a96f-a431b2a2c236] flavor, virt_type)
>
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
> 1840ac2e-5a54-4941-a96f-a431b2a2c236]   File "/usr/lib/python2.7/site-
> packages/nova/virt/libvirt/vif.py", line 374, in get_config
>
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
> 1840ac2e-5a54-4941-a96f-a431b2a2c236] _("Unexpected vif_type=%s") %
> vif_type)
>
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
> 1840ac2e-5a54-4941-a96f-a431b2a2c236] NovaException: Unexpected
> vif_type=binding_failed
>
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
> 1840ac2e-5a54-4941-a96f-a431b2a2c236]
>
>
>
> On Mon, Feb 20, 2017 at 12:31 PM, Melvin Hillsman 
> wrote:
>
>> Since the error was with scheduling you will want to modify the config
>> for nova to show verbose output, try to create another instance, and check
>> for the uuid and/or requestid of the creation attempt in the log -
>> nova-scheduler.log
>>
>> I would turn verbose logging off right after you get a failed attempt to
>> schedule as well since they logs can grow quickly.
>>
>> On Mon, Feb 20, 2017 at 12:56 AM, Saverio Proto  wro
>> te:
>>
>>> Well,
>>> I have no idea from this log file. Trying to make nova-compute more
>>> verbose if you dont find anything in the logs
>>>
>>> Saverio
>>>
>>> 2017-02-20 7:50 GMT+01:00 Anwar Durrani :
>>> >
>>> > On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto 
>>> wrote:
>>> >>
>>> >> openstack server show uuid
>>> >
>>> >
>>> > Hi Saverio,
>>> >
>>> > I have investigated and progressed the case as per your saying, i got
>>> to
>>> > know that instance was supposed to be launched on one of the nova node,
>>> > where i dig and tried find out log as you mentioned, following output
>>> i have
>>> > seen as below :
>>> >
>>> > tail -f /var/log/nova/nova-compute.log
>>> >
>>> > 2017-02-20 10:40:19.318 5365 WARNING nova.compute.manager
>>> > [req-34fa4448-061d-44ad-b6e9-6ff0d1fd072f - - - - -] While
>>> synchronizing
>>> > instance power states, found 4 instances in the database and 0
>>> instances on
>>> > the hypervisor.
>>> >
>>> > and
>>> >
>>> > other log where i have found following :
>>> >
>>> > tail -f /var/log/nova/nova-manage.log
>>> >
>>> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
>>> > "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 34,
>>> in
>>> > sleep
>>> >
>>> > 2017-02-15 16:42:42.896 115003 TRACE nova hub.switch()
>>> >
>>> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
>>> > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in
>>> switch
>>> >
>>> > 2017-02-15 16:42:42.896 115003 TRACE nova return
>>> self.greenlet.switch()
>>> >
>>> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
>>> > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 346, in
>>> run
>>> >
>>> > 2017-02-15 16:42:42.896 115003 TRACE nova self.wait(sleep_time)
>>> >
>>> >
>>> > Thanks
>>> >
>>> >
>>> >
>>> > --
>>> > Thanks & regards,
>>> > Anwar M. Durrani
>>> > +91-9923205011 <099232%2005011>
>>> >
>>> >
>>>
>>> ___
>>> OpenStack-operators mailing list
>>> OpenStack-operators@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>
>>
>>
>> --
>> Kind regards,
>>
>> Melvin Hillsman
>> Ops Technical Lead
>> OpenStack Innovation Center
>>
>> mrhills...@gmail.com
>> phone: (210) 312-1267
>> mobile: (210) 413-1659
>> http://osic.org
>>
>> Learner | Ideation | Belief | Responsibility | Command
>>
>
>
>
> --
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011

Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes

2017-02-20 Thread Kostyantyn Volenbovskyi 
Hi, 
this 'Unexpected vif_type=binding_failed’ is as well fairly-generic, but you 
can change focus from Nova to Neutron+virtual switch.

So check:
-Neutron server logs
-Logs of Neutron agent on target Compute Host(s)
-OVS logs and possibly things like /var/log/messages for things related to 
virtual networking.

The root cause is typically:
-misconfiguration of mechanism driver/type driver. 
-misconfiguration of virtual switching (typically OVS)
Go through installation documents in docs.openstack.org, that provides a guide 
for values 
parameters related to that.


BR, 
Konstantin

> On Feb 20, 2017, at 8:16 AM, Anwar Durrani  wrote:
> 
> Further when i tried and attempt to launch new instance, i can see the 
> following 
> 
> tail -f /var/log/nova/nova-compute.log 
> 
> 
> 
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance: 
> 1840ac2e-5a54-4941-a96f-a431b2a2c236] flavor, virt_type)
> 
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance: 
> 1840ac2e-5a54-4941-a96f-a431b2a2c236]   File 
> "/usr/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 374, in 
> get_config
> 
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance: 
> 1840ac2e-5a54-4941-a96f-a431b2a2c236] _("Unexpected vif_type=%s") % 
> vif_type)
> 
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance: 
> 1840ac2e-5a54-4941-a96f-a431b2a2c236] NovaException: Unexpected 
> vif_type=binding_failed
> 
> 2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance: 
> 1840ac2e-5a54-4941-a96f-a431b2a2c236] 
> 
> 
> 
> 
> 
> On Mon, Feb 20, 2017 at 12:31 PM, Melvin Hillsman  > wrote:
> Since the error was with scheduling you will want to modify the config for 
> nova to show verbose output, try to create another instance, and check for 
> the uuid and/or requestid of the creation attempt in the log - 
> nova-scheduler.log
> 
> I would turn verbose logging off right after you get a failed attempt to 
> schedule as well since they logs can grow quickly.
> 
> On Mon, Feb 20, 2017 at 12:56 AM, Saverio Proto  > wrote:
> Well,
> I have no idea from this log file. Trying to make nova-compute more
> verbose if you dont find anything in the logs
> 
> Saverio
> 
> 2017-02-20 7:50 GMT+01:00 Anwar Durrani  >:
> >
> > On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto  > > wrote:
> >>
> >> openstack server show uuid
> >
> >
> > Hi Saverio,
> >
> > I have investigated and progressed the case as per your saying, i got to
> > know that instance was supposed to be launched on one of the nova node,
> > where i dig and tried find out log as you mentioned, following output i have
> > seen as below :
> >
> > tail -f /var/log/nova/nova-compute.log
> >
> > 2017-02-20 10:40:19.318 5365 WARNING nova.compute.manager
> > [req-34fa4448-061d-44ad-b6e9-6ff0d1fd072f - - - - -] While synchronizing
> > instance power states, found 4 instances in the database and 0 instances on
> > the hypervisor.
> >
> > and
> >
> > other log where i have found following :
> >
> > tail -f /var/log/nova/nova-manage.log
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
> > "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 34, in
> > sleep
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova hub.switch()
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
> > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in switch
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova return self.greenlet.switch()
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
> > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 346, in run
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova self.wait(sleep_time)
> >
> >
> > Thanks
> >
> >
> >
> > --
> > Thanks & regards,
> > Anwar M. Durrani
> > +91-9923205011 
> >
> >
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators 
> 
> 
> 
> 
> -- 
> Kind regards,
> 
> Melvin Hillsman
> Ops Technical Lead
> OpenStack Innovation Center
> 
> mrhills...@gmail.com 
> phone: (210) 312-1267
> mobile: (210) 413-1659
> http://osic.org 
> 
> Learner | Ideation | Belief | Responsibility | Command
> 
> 
> 
> -- 
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011
>  
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org 
>

Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes

2017-02-19 Thread Anwar Durrani 
Further when i tried and attempt to launch new instance, i can see the
following

tail -f /var/log/nova/nova-compute.log


2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
1840ac2e-5a54-4941-a96f-a431b2a2c236] flavor, virt_type)

2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
1840ac2e-5a54-4941-a96f-a431b2a2c236]   File
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 374, in
get_config

2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
1840ac2e-5a54-4941-a96f-a431b2a2c236] _("Unexpected vif_type=%s") %
vif_type)

2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
1840ac2e-5a54-4941-a96f-a431b2a2c236] NovaException: Unexpected
vif_type=binding_failed

2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
1840ac2e-5a54-4941-a96f-a431b2a2c236]



On Mon, Feb 20, 2017 at 12:31 PM, Melvin Hillsman 
wrote:

> Since the error was with scheduling you will want to modify the config for
> nova to show verbose output, try to create another instance, and check for
> the uuid and/or requestid of the creation attempt in the log -
> nova-scheduler.log
>
> I would turn verbose logging off right after you get a failed attempt to
> schedule as well since they logs can grow quickly.
>
> On Mon, Feb 20, 2017 at 12:56 AM, Saverio Proto 
> wrote:
>
>> Well,
>> I have no idea from this log file. Trying to make nova-compute more
>> verbose if you dont find anything in the logs
>>
>> Saverio
>>
>> 2017-02-20 7:50 GMT+01:00 Anwar Durrani :
>> >
>> > On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto 
>> wrote:
>> >>
>> >> openstack server show uuid
>> >
>> >
>> > Hi Saverio,
>> >
>> > I have investigated and progressed the case as per your saying, i got to
>> > know that instance was supposed to be launched on one of the nova node,
>> > where i dig and tried find out log as you mentioned, following output i
>> have
>> > seen as below :
>> >
>> > tail -f /var/log/nova/nova-compute.log
>> >
>> > 2017-02-20 10:40:19.318 5365 WARNING nova.compute.manager
>> > [req-34fa4448-061d-44ad-b6e9-6ff0d1fd072f - - - - -] While
>> synchronizing
>> > instance power states, found 4 instances in the database and 0
>> instances on
>> > the hypervisor.
>> >
>> > and
>> >
>> > other log where i have found following :
>> >
>> > tail -f /var/log/nova/nova-manage.log
>> >
>> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
>> > "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 34, in
>> > sleep
>> >
>> > 2017-02-15 16:42:42.896 115003 TRACE nova hub.switch()
>> >
>> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
>> > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in
>> switch
>> >
>> > 2017-02-15 16:42:42.896 115003 TRACE nova return
>> self.greenlet.switch()
>> >
>> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
>> > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 346, in
>> run
>> >
>> > 2017-02-15 16:42:42.896 115003 TRACE nova self.wait(sleep_time)
>> >
>> >
>> > Thanks
>> >
>> >
>> >
>> > --
>> > Thanks & regards,
>> > Anwar M. Durrani
>> > +91-9923205011 <099232%2005011>
>> >
>> >
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
>
> --
> Kind regards,
>
> Melvin Hillsman
> Ops Technical Lead
> OpenStack Innovation Center
>
> mrhills...@gmail.com
> phone: (210) 312-1267
> mobile: (210) 413-1659
> http://osic.org
>
> Learner | Ideation | Belief | Responsibility | Command
>



-- 
Thanks & regards,
Anwar M. Durrani
+91-9923205011

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes

2017-02-19 Thread Melvin Hillsman 
Since the error was with scheduling you will want to modify the config for
nova to show verbose output, try to create another instance, and check for
the uuid and/or requestid of the creation attempt in the log -
nova-scheduler.log

I would turn verbose logging off right after you get a failed attempt to
schedule as well since they logs can grow quickly.

On Mon, Feb 20, 2017 at 12:56 AM, Saverio Proto  wrote:

> Well,
> I have no idea from this log file. Trying to make nova-compute more
> verbose if you dont find anything in the logs
>
> Saverio
>
> 2017-02-20 7:50 GMT+01:00 Anwar Durrani :
> >
> > On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto 
> wrote:
> >>
> >> openstack server show uuid
> >
> >
> > Hi Saverio,
> >
> > I have investigated and progressed the case as per your saying, i got to
> > know that instance was supposed to be launched on one of the nova node,
> > where i dig and tried find out log as you mentioned, following output i
> have
> > seen as below :
> >
> > tail -f /var/log/nova/nova-compute.log
> >
> > 2017-02-20 10:40:19.318 5365 WARNING nova.compute.manager
> > [req-34fa4448-061d-44ad-b6e9-6ff0d1fd072f - - - - -] While synchronizing
> > instance power states, found 4 instances in the database and 0 instances
> on
> > the hypervisor.
> >
> > and
> >
> > other log where i have found following :
> >
> > tail -f /var/log/nova/nova-manage.log
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
> > "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 34, in
> > sleep
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova hub.switch()
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
> > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in
> switch
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova return
> self.greenlet.switch()
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova   File
> > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 346, in
> run
> >
> > 2017-02-15 16:42:42.896 115003 TRACE nova self.wait(sleep_time)
> >
> >
> > Thanks
> >
> >
> >
> > --
> > Thanks & regards,
> > Anwar M. Durrani
> > +91-9923205011
> >
> >
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Kind regards,

Melvin Hillsman
Ops Technical Lead
OpenStack Innovation Center

mrhills...@gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659
http://osic.org

Learner | Ideation | Belief | Responsibility | Command
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes

2017-02-19 Thread Saverio Proto 
Well,
I have no idea from this log file. Trying to make nova-compute more
verbose if you dont find anything in the logs

Saverio

2017-02-20 7:50 GMT+01:00 Anwar Durrani :
>
> On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto  wrote:
>>
>> openstack server show uuid
>
>
> Hi Saverio,
>
> I have investigated and progressed the case as per your saying, i got to
> know that instance was supposed to be launched on one of the nova node,
> where i dig and tried find out log as you mentioned, following output i have
> seen as below :
>
> tail -f /var/log/nova/nova-compute.log
>
> 2017-02-20 10:40:19.318 5365 WARNING nova.compute.manager
> [req-34fa4448-061d-44ad-b6e9-6ff0d1fd072f - - - - -] While synchronizing
> instance power states, found 4 instances in the database and 0 instances on
> the hypervisor.
>
> and
>
> other log where i have found following :
>
> tail -f /var/log/nova/nova-manage.log
>
> 2017-02-15 16:42:42.896 115003 TRACE nova   File
> "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 34, in
> sleep
>
> 2017-02-15 16:42:42.896 115003 TRACE nova hub.switch()
>
> 2017-02-15 16:42:42.896 115003 TRACE nova   File
> "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in switch
>
> 2017-02-15 16:42:42.896 115003 TRACE nova return self.greenlet.switch()
>
> 2017-02-15 16:42:42.896 115003 TRACE nova   File
> "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 346, in run
>
> 2017-02-15 16:42:42.896 115003 TRACE nova self.wait(sleep_time)
>
>
> Thanks
>
>
>
> --
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011
>
>

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes

2017-02-19 Thread Anwar Durrani 
On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto  wrote:

> openstack server show uuid


​Hi Saverio,

I have investigated and progressed the case as per your saying, i got to
know that instance was supposed to be launched on one of the nova node,
where i dig and tried find out log as you mentioned, following output i
have seen as below :

tail -f /var/log/nova/nova-compute.log
2017-02-20 10:40:19.318 5365 WARNING nova.compute.manager
[req-34fa4448-061d-44ad-b6e9-6ff0d1fd072f - - - - -] While synchronizing
instance power states, found 4 instances in the database and 0 instances on
the hypervisor.

and

other log where i have found following :

tail -f /var/log/nova/nova-manage.log

2017-02-15 16:42:42.896 115003 TRACE nova   File
"/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 34, in
sleep

2017-02-15 16:42:42.896 115003 TRACE nova hub.switch()

2017-02-15 16:42:42.896 115003 TRACE nova   File
"/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in switch

2017-02-15 16:42:42.896 115003 TRACE nova return self.greenlet.switch()

2017-02-15 16:42:42.896 115003 TRACE nova   File
"/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 346, in run

2017-02-15 16:42:42.896 115003 TRACE nova self.wait(sleep_time)

Thanks​



-- 
Thanks & regards,
Anwar M. Durrani
+91-9923205011

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes

2017-02-16 Thread Saverio Proto 
The three new compute nodes that you added are empty, so most likely
the new instances are scheduled to those three (3 attempts) and
something goes wrong.

with admin rights do:
openstack server show uuid

this should give you the info about the compute node where the
instance was scheduled. Check the nova-compute.log of that one, you
should find some debug info.

Saverio


2017-02-16 8:40 GMT+01:00 Anwar Durrani :
> Hi team,
>
> I am running Kilo setup with 1 Controller and 7 nova nodes, i have added 3
> additional nova nodes, where i can see, in system information under compute
> nodes that nodes are up and running, but when i am trying to launch instance
> then it is prompting below error :
>
> Error: Failed to perform requested operation on instance "test", the
> instance has an error status: Please try again later [Error: No valid host
> was found. Exceeded max scheduling attempts 3 for instance
> 969e71d4-845a-40da-be2a-d4f2619cbc68. Last exception: [u'Traceback (most
> recent call last):\n', u' File
> "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2248, in
> _do].
>
>
> Thanks in advance.
>
>
> --
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011
>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Instances are not creating after adding 3 additional nova nodes

2017-02-15 Thread Anwar Durrani 
Hi team,

I am running Kilo setup with 1 Controller and 7 nova nodes, i have added 3
additional nova nodes, where i can see, in system information under compute
nodes that nodes are up and running, but when i am trying to launch
instance then it is prompting below error :

*Error: *Failed to perform requested operation on instance "test", the
instance has an error status: Please try again later [Error: No valid host
was found. Exceeded max scheduling attempts 3 for instance
969e71d4-845a-40da-be2a-d4f2619cbc68. Last exception: [u'Traceback (most
recent call last):\n', u' File
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2248, in
_do].


Thanks in advance.

-- 
Thanks & regards,
Anwar M. Durrani
+91-9923205011

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators