[OVSDB-369] Failed to process back to back config updates Created: 30/Aug/16  Updated: 30/Oct/17  Resolved: 23/Jan/17

Status: Resolved
Project: ovsdb
Component/s: Southbound.hw_vtep
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: suneel verma Assignee: Vishal Thapar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 6579

 Description   

Consider the following backto back mcast mac updates.

Remote Mcast Mac

{ unknown-dst, ls0, [TEPIP1, TEPIP2] }

Remote Mcast Mac

{ unknown-dst, ls0, [TEPIP1, TEPIP2, TEPIP3] }

Remote Ucast Mac

{ 10:10:10:10:10:10, ls0, TEPIP3 }

second and third update are not processed properly and device is not having the ucast mac

 Comments   
Comment by suneel verma [ 30/Aug/16 ]

To add more context to the bug

Consider TEP2 is 192.168.122.50
TEP3 is 192.168.122.60

The first update is doing the following
Creating a physical locator: IpAddress [_ipv4Address=Ipv4Address [_value=192.168.122.50]]

create RemoteMcastMac entry: Mcast_Macs_Remote : Row [columns=

{locator_set=[locator_set=PhysicalLocatorSet_Random_95f6f15453644ea58d85a233324b7b89], ipaddr=[ipaddr=3.3.3.5], logical_switch=[logical_switch=ef000b24-af2e-43f0-9a07-95f56e98fa67], MAC=[MAC=33:33:33:33:33:55]}

]

It succeeds

The second update will again try to create physical locator 192.168.122.50
Creating a physical locator: IpAddress [_ipv4Address=Ipv4Address [_value=192.168.122.50]]

create RemoteMcastMac entry: Mcast_Macs_Remote : Row [columns=

{locator_set=[locator_set=PhysicalLocatorSet_Random_741c411bf3f9434e8143cd4f08cb5113], ipaddr=[ipaddr=3.3.3.5], logical_switch=[logical_switch=ef000b24-af2e-43f0-9a07-95f56e98fa67], MAC=[MAC=33:33:33:33:33:55]}

]

this fails with the below error.
operation failed constraint violation Transaction causes multiple rows in "Physical_Locator" table to have identical values ("vxlan_over_ipv4" and "192.168.122.50") for index on columns "encapsulation_type" and "dst_ip". First row, with UUID cba85c3d-0b79-4e1b-ac77-76b534911d35, was inserted by this transaction. Second row, with UUID 3a4493ad-bd47-4c8a-9ab7-86bd3ac21280, existed in the database before this transaction and was not modified by the transaction.

Comment by Vishal Thapar [ 31/Aug/16 ]

Best way to fix this would require OVSDB-348 to be fixed first. On getting notification of failed transaction need to resubmit this one as an update.

Comment by Vishal Thapar [ 23/Jan/17 ]

https://git.opendaylight.org/gerrit/#/q/topic:bug/6579

Generated at Wed Feb 07 20:36:13 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.