openvswitch set-manager to ODL doesn't work

Bug #1637928 reported by Vu Nguyen Duy (CBR09)
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla
Invalid
Low
Unassigned

Bug Description

Hi,
I've installed OpenStack newton with kolla, everything work fine, but I want to integrate neutron with opendaylight, so I had to set openvswitch's manager to ODL controller, I had to docker exec into openvswitch-vswitchd or openvswitch-db-server and ran "ovs-vsctl set-manager tcp:x.x.x.x:6640" (x.x.x.x is IP of ODL controller), but nothing happen, no log. I've just have (is_connected: false):
(openvswitch-db)[root@abc /]# ovs-vsctl list manager
_uuid : c0c22173-18af-4fac-8237-8c2c6be06db9
connection_mode : []
external_ids : {}
inactivity_probe : []
is_connected : false
max_backoff : []
other_config : {}
status : {}
target : "tcp:x.x.x.x:6640"

Someone told me due to selinux but I don't know how to turn off selinux in kolla openvswitch container (update: selinux on host turned off). Beside I tried to run another ubuntu 16.04 container, installed openvswitch and ran set-manager, it worked. I wonder how can I set-manager to ODL controller in kolla openvswitch container?. How can I debug?
Thanks

description: updated
description: updated
description: updated
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

no idea about ODL.
But you can disable selinux on host OS direct, then you can run a test.

# setenforce 0

Changed in kolla:
status: New → Triaged
milestone: none → ocata-1
Revision history for this message
Vu Nguyen Duy (CBR09) (nguyenduyvu099) wrote :

Hi,
I turned off selinux on host OS, but I still can't set manager in kolla openvswitch containers

description: updated
description: updated
description: updated
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

could u check the log
* docker logs openvswitch_db
* docker logs openvsiwtch_vswitch
* /var/lib/docker/volumes/kolla_logs/_data/

if there any error raise during run `ovs-vsctl set-manager`

normally it should work the same on different host OS. if it not, there should be some mis-configure in host OS i think.

Revision history for this message
Vu Nguyen Duy (CBR09) (nguyenduyvu099) wrote :

There are nothing in logs during run `ovs-vsctl set-manager` :(
root@abc:~# docker logs -f openvswitch_db
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Writing out command to execute
Running command: 'start-ovsdb-server x.x.x.x '

root@abc:~# tail -f /var/lib/docker/volumes/kolla_logs/_data/openvswitch/*
==> /var/lib/docker/volumes/kolla_logs/_data/openvswitch/ovsdb-server.log <==
2016-11-03T06:45:03.273Z|00001|vlog|INFO|opened log file /var/log/kolla/openvswitch/ovsdb-server.log
2016-11-03T06:45:03.314Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 2.6.0
2016-11-03T06:45:13.317Z|00003|memory|INFO|4776 kB peak resident set size after 10.0 seconds
2016-11-03T06:45:13.317Z|00004|memory|INFO|cells:595 json-caches:1 monitors:2 sessions:2

==> /var/lib/docker/volumes/kolla_logs/_data/openvswitch/ovs-vswitchd.log <==
2016-11-03T06:45:12.251Z|00037|connmgr|INFO|br-tun: added primary controller "tcp:127.0.0.1:6633"
2016-11-03T06:45:12.251Z|00038|rconn|INFO|br-tun<->tcp:127.0.0.1:6633: connecting...
2016-11-03T06:45:12.261Z|00039|rconn|INFO|br-tun<->tcp:127.0.0.1:6633: connected
2016-11-03T06:45:12.476Z|00040|bridge|INFO|bridge br-int: added interface patch-tun on port 2
2016-11-03T06:45:12.598Z|00041|bridge|INFO|bridge br-tun: added interface patch-int on port 1
2016-11-03T06:45:15.157Z|00042|memory|INFO|50724 kB peak resident set size after 10.1 seconds
2016-11-03T06:45:15.157Z|00043|memory|INFO|handlers:2 ofconns:3 ports:8 revalidators:2 rules:30 udpif keys:1
2016-11-03T06:45:20.963Z|00044|connmgr|INFO|br-int<->tcp:127.0.0.1:6633: 4 flow_mods 10 s ago (4 adds)
2016-11-03T06:45:21.528Z|00045|connmgr|INFO|br-ex<->tcp:127.0.0.1:6633: 2 flow_mods 10 s ago (2 adds)
2016-11-03T06:45:22.718Z|00046|connmgr|INFO|br-tun<->tcp:127.0.0.1:6633: 12 flow_mods 10 s ago (12 adds)

root@abc:~# docker logs -f openvswitch_db
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Writing out command to execute
Running command: 'start-ovsdb-server x.x.x.x '

Changed in kolla:
milestone: ocata-1 → ocata-2
Changed in kolla:
milestone: ocata-2 → ocata-3
Changed in kolla:
status: Triaged → Incomplete
importance: Undecided → Low
Revision history for this message
Khawar Munir Abbasi (ekhawmu) wrote :

Which ODL release are you using? If you are using Boron, have you tried it with odl-netvirt-openstack plugin rather than odl-ovsdb-openstack?

Revision history for this message
Vu Nguyen Duy (CBR09) (nguyenduyvu099) wrote :

Sorry for my late response, I'm using ODL boron and carbon, mean use new netvirt project: odl-netvirt-openstack. I don't know why kolla openvswitch container didn't work, but my workaround is stopped and removed all kolla openvswitch containers, and starting own openvswitch container, hope it useful to you.

Mark Goddard (mgoddard)
Changed in kolla:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.