[GENIUS-276] updateDpnTepInterfaceInfoToConfig doesn't update dpnTepsState correctly Created: 09/May/19 Updated: 08/Jan/20 Resolved: 08/Jan/20 |
|
| Status: | Resolved |
| Project: | genius |
| Component/s: | ITM |
| Affects Version/s: | None |
| Fix Version/s: | Neon |
| Type: | Bug | Priority: | High |
| Reporter: | Yi Yang | Assignee: | nidhi adhvaryu |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
genius master |
||
| Priority: | Highest |
| Description |
|
Although updateDpnTepInterfaceInfoToConfig called ITMBatchingUtils.update to change dpnTepsState per srcDpnId, but ResourceBatchingManager will overwrite the old one with new one, new one doesn't contain the old one, this can be read out from source code. case ActionableResource.UPDATE: Because we don't setOldInstance when call ITMBatchingUtils.update. The actual test result has confirmed this. vagrant@odl:~/karaf-0.9.0-SNAPSHOT$ grep ", remoteDpn TunnelName " data/log/karaf.log |
| Comments |
| Comment by Yi Yang [ 10/May/19 ] |
|
vagrant@odl:~/karaf-0.9.0-SNAPSHOT$ grep -r "addTunnelEndPointInfoToCache" data/log/karaf.log My test has testified this, https://git.opendaylight.org/gerrit/#/c/81966/ did fix it. addTunnelEndPointInfoToCache: call added, tunnel tuna6d316383be, src dpn 251290173143295, dst dpn 207790482554426 |
| Comment by nidhi adhvaryu [ 08/Jan/20 ] |
|
this issue occurs, when computes were scaled-in and scaled-out with the same vtep ip, ITM full mesh was not created.During scale-in, ITM caches were not completely cleaned up resulting in stale DPN in ITM. This prevented the full mesh creation. So this, https://git.opendaylight.org/gerrit/#/c/genius/+/81888/ patch has addressed the issue. the patch is merged already. |
| Comment by nidhi adhvaryu [ 08/Jan/20 ] |
|
fix is already merged on https://git.opendaylight.org/gerrit/#/c/genius/+/81888/ |