Praveen, 
there are many error in your q-svc log.
It says:

InvalidInput: Invalid input for operation: (u'Tunnel IP %(ip)s in use
with host %(host)s', {'ip': u'10.81.1.150', 'host':
u'localhost.localdomain'}).\n"]


Did you maybe specify duplicated ips in your controllers and compute
nodes neutron tunnel config?

Or did you change the hostname after installation

Or maybe the code has trouble with duplicated host names?

-- 
Andreas
(IRC: scheuran)



On Di, 2015-11-24 at 15:28 +0100, Praveen MANKARA RADHAKRISHNAN wrote:
> Hi Sean, 
> 
> 
> Thanks for the reply. 
> 
> 
> Please find the logs attached. 
> ovs-dpdk is correctly running in compute.
> 
> 
> Thanks
> Praveen 
> 
> On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K
> <sean.k.moo...@intel.com> wrote:
>         Hi would you be able to attach the
>         
>         n-cpu log form the computenode  and  the
>         
>         n-sch and q-svc logs for the controller so we can see if there
>         is a stack trace relating to the
>         
>         vm boot.
>         
>          
>         
>         Also can you confirm ovs-dpdk is running correctly on the
>         compute node by running 
>         
>         sudo service ovs-dpdk status
>         
>          
>         
>         the neutron and networking-ovs-dpdk commits are from their
>         respective stable/kilo branches so they should be compatible
>         
>         provided no breaking changes have been merged to either
>         branch.
>         
>          
>         
>         regards
>         
>         sean.
>         
>          
>         
>         From: Praveen MANKARA RADHAKRISHNAN
>         [mailto:praveen.mank...@6wind.com] 
>         Sent: Tuesday, November 24, 2015 1:39 PM
>         To: OpenStack Development Mailing List (not for usage
>         questions)
>         Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation
>         fails with Unexpected vif_type=binding_failed
>         
>          
>         
>         Hi Przemek,
>         
>          
>         
>         
>         Thanks For the response, 
>         
>         
>          
>         
>         
>         Here are the commit ids for Neutron and networking-ovs-dpdk 
>         
>         
>          
>         
>         
>         [stack@localhost neutron]$ git log --format="%H" -n 1
>         
>         
>         026bfc6421da796075f71a9ad4378674f619193d
>         
>         
>         [stack@localhost neutron]$ cd ..
>         
>         
>         [stack@localhost ~]$ cd networking-ovs-dpdk/
>         
>         
>         [stack@localhost networking-ovs-dpdk]$  git log --format="%H"
>         -n 1
>         
>         
>         90dd03a76a7e30cf76ecc657f23be8371b1181d2
>         
>         
>          
>         
>         
>         The Neutron agents are up and running in compute node. 
>         
>         
>          
>         
>         
>         Thanks 
>         
>         
>         Praveen
>         
>         
>          
>         
>         
>          
>         
>         On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw
>         <przemyslaw.czesnow...@intel.com> wrote:
>         
>                 Hi Praveen,
>                 
>                  
>                 
>                 There’s been some changes recently to
>                 networking-ovs-dpdk, it no longer host’s a mech driver
>                 as the openviswitch mech driver in Neutron supports
>                 vhost-user ports.
>                 
>                 I guess something went wrong and the version of
>                 Neutron is not matching networking-ovs-dpdk. Can you
>                 post commit ids of Neutron and networking-ovs-dpdk.
>                 
>                  
>                 
>                 The other possibility is that the Neutron agent is not
>                 running/died on the compute node.
>                 
>                 Check with:
>                 
>                 neutron agent-list
>                 
>                  
>                 
>                 Przemek
>                 
>                  
>                 
>                 From: Praveen MANKARA RADHAKRISHNAN
>                 [mailto:praveen.mank...@6wind.com] 
>                 Sent: Tuesday, November 24, 2015 12:18 PM
>                 To: openstack-dev@lists.openstack.org
>                 Subject: [openstack-dev] [networking-ovs-dpdk] VM
>                 creation fails with Unexpected vif_type=binding_failed
>                 
>                 
>                  
>                 
>                 Hi,
>                 
>                  
>                 
>                 
>                 Am trying to set up an open stack (kilo) installation
>                 using ovs-dpdk through devstack installation. 
>                 
>                 
>                  
>                 
>                 
>                 I have followed the "
>                 
> https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst
>  " documentation. 
>                 
>                 
>                  
>                 
>                 
>                 I used the same versions as in documentation
>                 (fedora21, with right kernel). 
>                 
>                 
>                  
>                 
>                 
>                 My openstack installation is successful in both
>                 controller and compute. 
>                 
>                 
>                 I have used example local.conf given in the
>                 documentation. 
>                 
>                 
>                 But if i try to spawn the VM. I am having the
>                 following error. 
>                 
>                 
>                  
>                 
>                 
>                 "NovaException: Unexpected vif_type=binding_failed" 
>                 
>                 
>                  
>                 
>                 
>                 It would be really helpful if you can point out how to
>                 debug and fix this error. 
>                 
>                 
>                  
>                 
>                 
>                 Thanks
>                 
>                 
>                 Praveen
>                 
>                 
>                  
>                 
>                 
>                 
>                 
> __________________________________________________________________________
>                 OpenStack Development Mailing List (not for usage
>                 questions)
>                 Unsubscribe:
>                 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>                 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>                 
>          
>         
>         
>         
>         
> __________________________________________________________________________
>         OpenStack Development Mailing List (not for usage questions)
>         Unsubscribe:
>         openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>         
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to