Description of problem:
 
Saw the following repeated errors for about five minutes. The messages log indicated that "ovs-vsctl" was run about five minutes ahead of openvswitch.init.

network[798]: 2012-10-01T00:42:38Z|00048|stream_unix|ERR|/var/run/openvswitch/db.sock: connection failed (No such file or directory)
network[798]: 2012-10-01T00:42:38Z|00049|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (No such file or directory)
network[798]: 2012-10-01T00:42:46Z|00050|stream_unix|ERR|/var/run/openvswitch/db.sock: connection failed (No such file or directory)
network[798]: 2012-10-01T00:42:46Z|00051|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (No such file or directory)
network[798]: 2012-10-01T00:42:54Z|00052|stream_unix|ERR|/var/run/openvswitch/db.sock: connection failed (No such file or directory)
network[798]: 2012-10-01T00:42:54Z|00053|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (No such file or directory)

Version-Release number of selected component (if applicable):
openvswitch: 1.17.1

How reproducible: very reproducible


Steps to Reproduce:
1.Install openvswitch.
2.Configured an openvswitch.
3.Ran "systemctl enable openvswitch.service".
4. Reboot system
  
Actual results:
openvswitch.init ran ~5 minutes later than "ovs-vsctl add-br". This resulted in the connection failure errors lasting for ~5 minutes.

Expected results:

openvswitch.init should run before "ovs-vsctl add-br". This will eliminate the connetion failure errors.
Additional info: