On Wed, May 18, 2016 at 06:05:14AM -0400, Aaron Conole wrote:
> Ben Pfaff writes:
>
> > On Mon, May 02, 2016 at 01:08:53PM -0400, Aaron Conole wrote:
> >> The ovs-ctl script was changed recently to have per-service start/stop
> >> control. However, when that change was made the add_managers() cal
Ben Pfaff writes:
> On Mon, May 02, 2016 at 01:08:53PM -0400, Aaron Conole wrote:
>> The ovs-ctl script was changed recently to have per-service start/stop
>> control. However, when that change was made the add_managers() call was
>> overlooked. This results in calls to `ovs-ctl --no-ovs-vswitchd
On Mon, May 02, 2016 at 01:08:53PM -0400, Aaron Conole wrote:
> The ovs-ctl script was changed recently to have per-service start/stop
> control. However, when that change was made the add_managers() call was
> overlooked. This results in calls to `ovs-ctl --no-ovs-vswitchd start`
> telling the ovs
Aaron Conole writes:
> The ovs-ctl script was changed recently to have per-service start/stop
> control. However, when that change was made the add_managers() call was
> overlooked. This results in calls to `ovs-ctl --no-ovs-vswitchd start`
> telling the ovsdb-server to connect to the remote cont
The ovs-ctl script was changed recently to have per-service start/stop
control. However, when that change was made the add_managers() call was
overlooked. This results in calls to `ovs-ctl --no-ovs-vswitchd start`
telling the ovsdb-server to connect to the remote controllers.
This commit disables
