When synching from a database that doesn't exist, the entire database will wipe. This is obviously very bad, because synching is typically used to handle scenarios where a service is unreachable.
Actions:
1. Start ovn-central via 'service ovn-central start'
2. Add an item to the database via 'ovn-nbctl ls-add'
3. Start synching by the running the synch commands below. Make sure the IP/PORT combination you choose does NOT point to an ovsdb instance.
ovs-appctl -t /var/run/openvswitch/ovnnb_db.ctl ovsdb-server/set-remote-ovsdb-server tcp:{IP}:{PORT}
ovs-appctl -t /var/run/openvswitch/ovnnb_db.ctl ovsdb-server/connect-remote-ovsdb-server
4. Run 'ovn-nbctl show'
Expected result:
View the switch that was added
Actual result:
The database is empty, and the command takes longer then expected to return.
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
