Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-05 Thread pranab boruah
Hi Numan, Thanks for the input. I did a fresh install again and used an older OVS 2.6 package.(not using the TOT). Things are working now. Pranab On 2 February 2017 at 19:19, Numan Siddique wrote: > > > On Thu, Feb 2, 2017 at 6:05 PM, pranab boruah

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread Numan Siddique
On Thu, Feb 2, 2017 at 6:05 PM, pranab boruah wrote: > Numan, > Sorry for making this thread too long. > Kind of deadlock scenario here: > The process listening on port 6641 is ovsdb-server(not NB db). > ​This is strange. The default port should be 6640 I suppose if

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread pranab boruah
Numan, Sorry for making this thread too long. Kind of deadlock scenario here: The process listening on port 6641 is ovsdb-server(not NB db). Details: Start OVS: # /usr/share/openvswitch/scripts/ovs-ctl start --system-id="random" # netstat -putna | grep 6641 tcp0 0 192.168.10.10:6641

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread Numan Siddique
In the ovsdb logs I see 2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10: bind: Address already in use 2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10: bind: Address already in use 2017-02-02T11:07:16.182Z|00022|socket_util|ERR|6641:192.168.10.10: bind: Address

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread pranab boruah
NB db is not listening on the port 6641: # ovn-nbctl --db=tcp:192.168.10.10:6641 show 2017-02-02T11:35:10Z|1|ovsdb_idl|ERR|tcp:192.168.10.10:6641: requested schema not found ovn-nbctl: tcp:192.168.10.10:6641: database connection failed (No such file or directory) # ovn-sbctl

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread Numan Siddique
On Thu, Feb 2, 2017 at 4:44 PM, pranab boruah wrote: > Numan, > > Thanks, but, the above commands didn't changed anything. Checked the logs > and found this: > > ​ Could you run the below two commands and see how it goes - "ovn-nbctl --db=tcp:192.168.10.10:6641

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread pranab boruah
Numan, Thanks, but, the above commands didn't changed anything. Checked the logs and found this: LOG of NB database: 2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10: bind: Address already in use 2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10: bind: Address

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread Numan Siddique
On Thu, Feb 2, 2017 at 4:00 PM, pranab boruah wrote: > Numan, > Details as requested: > > ___ > ml2_conf.ini:| > ``` > ovn_nb_connection = tcp:192.168.10.10:6641 > ovn_sb_connection = tcp:192.168.10.10:6642 > ovn_l3_mode = True >

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread pranab boruah
Numan, Details as requested: ___ ml2_conf.ini:| ``` ovn_nb_connection = tcp:192.168.10.10:6641 ovn_sb_connection = tcp:192.168.10.10:6642 ovn_l3_mode = True ovn_l3_scheduler = chance ovn_l3_admin_net_cidr = 169.254.128.0/30 ovn_native_dhcp = True Note: 192.168.10.10 is

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-02 Thread Numan Siddique
Adding openstack-dev ML with [networking-ovn] tag. Please see comments inline On Thu, Feb 2, 2017 at 3:01 PM, pranab boruah wrote: > Hi guys, > We have a OpenStack multi-node lab. Everything was working, until I tried > integrating with OVN. > Followed the