Hello folks,
I am part of kolla-kubernetes project, our goal is to deliver deployment and
lifecycle tools for OpenStack in Kubernetes environment. We are part of Kolla
community, I am sure you heard about.
During the development, we hit an issue with ovsdb-server, in some cases it
comes up but does not create db named socket which we need so other process
could communicate with ovsdb-server.
Here is my ovsdb initialization sequence: (the empty database has already been
created and located in /etc/openvswitch/conf.db)
echo "Creating external bridge..."
/usr/sbin/ovsdb-server /etc/openvswitch/conf.db
--remote=punix:/run/openvswitch/db.sock --run="ovs-vsctl --no-wait
--db=unix:/run/openvswitch/db.sock add-br $ovs_bridge"
echo "Plug the external interface..."
/usr/sbin/ovsdb-server /etc/openvswitch/conf.db
--remote=punix:/run/openvswitch/db.sock --run="ovs-vsctl --no-wait
--db=unix:/run/openvswitch/db.sock add-port $ovs_bridge $ovs_ext_intf"
echo "Run ovsdb server proces..."
/usr/sbin/ovsdb-server /etc/openvswitch/conf.db -vconsole:emer -vsyslog:err
-vfile:info --remote=punix:/run/openvswitch/db.sock
--log-file=/var/log/kolla/openvswitch/ovsdb-server.log
As I mentioned the issue is very intermittent and so far I could not detect any
patterns. I was wondering if you could help in getting the root cause of this
issue. There is a good possibility that the issue is on Kubernetes side, but we
need to confirm it.
I would appreciate if somebody from OVS community could build debug
ovsdb-server and ovs-vsctl images based on 2.5.0 code base with extensive
debugging/logging, hopefully it will help to narrow down the direction of
further troubleshooting.
This issue has already been reported by other folks from kubernetes community,
so resolving it would mean a lot not just to our project but also kubernetes
folks. I hope OVS community is interested in proilifiration of OVS on
additional platforms.
Kubernetes cluster runs on 5 nodes, 2 of which are compute nodes where
ovsdb-server runs. Ovs 2.5.0 rpm is used to install ovs components onto centos
7.2 based docker image which then launched inside of a kubernetes pod by means
of daemonsets.
If somebody is interested I can organize a demonstration of the issue with
ddebugging session. I really hope my request to get debugging image will not go
unanswered.
Thank you for your help
Serguei
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
