Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.6.2
-
None
-
Triaged
-
Unknown
Description
It appears that our conflict resolution as part of config sync is not perfectly convergent. We have seen cases where nodes can ping-pong on conflicting changes to the config.
Attachments
For Gerrit Dashboard: MB-25004 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
80408,3 | MB-25004 consider timestamps equal if they differ by 10sec | watson | ns_server | Status: ABANDONED | 0 | +1 |
83364,2 | MB-25004 do not increment timestamp when merging 2 conflicting values | master | ns_server | Status: MERGED | +2 | +1 |