You are right, this is a bug.
I reverted the commit.
On Tue, Feb 12, 2013 at 12:01:04PM -0600, Saul St. John wrote:
> Previously, I was able to set setup multiple bridges on the same host to
> talk to the same controller like this:
>
> # ovs-vsctl set-controller br0 tcp:10.0.0.1:6633
> # ovs
Previously, I was able to set setup multiple bridges on the same host to
talk to the same controller like this:
# ovs-vsctl set-controller br0 tcp:10.0.0.1:6633
# ovs-vsctl set-controller br1 tcp:10.0.0.1:6633
and it worked. Now, when I try to do that, I get this error:
ovs-vsctl: transact
Thank you, I applied this to master.
On Mon, Feb 04, 2013 at 01:00:52PM -0800, Ethan Jackson wrote:
> Acked-by: Ethan Jackson
>
> On Fri, Feb 1, 2013 at 2:51 PM, Ben Pfaff wrote:
> > Commit cc7ecee48 (vswitchd: Add unique indexes for some columns.) says,
> > in part:
> >
> > With this commi
Acked-by: Ethan Jackson
On Fri, Feb 1, 2013 at 2:51 PM, Ben Pfaff wrote:
> Commit cc7ecee48 (vswitchd: Add unique indexes for some columns.) says,
> in part:
>
> With this commit, the database server itself rejects attempts to add
> Port or Interface records with duplicate names or Contr
Commit cc7ecee48 (vswitchd: Add unique indexes for some columns.) says,
in part:
With this commit, the database server itself rejects attempts to add
Port or Interface records with duplicate names or Controller or
Manager records with duplicate targets.
but in fact didn't change the C
Commit cc7ecee48 (vswitchd: Add unique indexes for some columns.) says,
in part:
With this commit, the database server itself rejects attempts to add
Port or Interface records with duplicate names or Controller or
Manager records with duplicate targets.
but in fact didn't change the C
