Open Stack

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 <durrani.anwar at gmail.com> 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 <mrhillsman at gmail.com <mailto:mrhillsman at gmail.com>> 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 <zioproto at gmail.com <mailto:zioproto at gmail.com>> 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 <durrani.anwar at gmail.com <mailto:durrani.anwar at gmail.com>>:
> >
> > On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto <zioproto at gmail.com <mailto:zioproto at gmail.com>> 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 <tel:099232%2005011>
> >
> >
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org <mailto:OpenStack-operators at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
> 
> 
> 
> -- 
> Kind regards,
> 
> Melvin Hillsman
> Ops Technical Lead
> OpenStack Innovation Center
> 
> mrhillsman at gmail.com <mailto:mrhillsman at gmail.com>
> phone: (210) 312-1267
> mobile: (210) 413-1659
> http://osic.org <http://osic.org/>
> 
> Learner | Ideation | Belief | Responsibility | Command
> 
> 
> 
> -- 
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011
>  <http://in.linkedin.com/pub/anwar-durrani/20/b55/60b>
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org <mailto:OpenStack-operators at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170220/9b985588/attachment.html>