[GENIUS-257] LockManager eternally retries? Created: 17/Dec/18 Updated: 19/Dec/19 Resolved: 19/Dec/19 |
|
| Status: | Verified |
| Project: | genius |
| Component/s: | None |
| Affects Version/s: | Neon |
| Fix Version/s: | Sodium |
| Type: | Bug | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Amitesh Soni |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 2 weeks | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
While working on 2018-12-17T17:48:48,035 | INFO | jobcoordinator-main-task-6 | LockManagerServiceImpl | 265 - org.opendaylight.genius.lockmanager-impl - 0.6.0.SNAPSHOT | Waiting for the lock interfacesvethb906f0c0 is timed out. retrying again 2018-12-17T17:48:48,036 | WARN | jobcoordinator-main-task-6 | LockManagerServiceImpl | 265 - org.opendaylight.genius.lockmanager-impl - 0.6.0.SNAPSHOT | Already locked for interfacesvethb906f0c0 after waiting 1000ms, try 71 This may have been because of some dev env related thing, like I may not have had the Watcher continously running once I delete busybox test Pod or something like that, but we probably still should never get into this kind of endless retry loops? FYI k.faseela, shague, fkautz. |
| Comments |
| Comment by Michael Vorburger [ 17/Dec/18 ] |
|
The INFO / WARN cycle stopped when I re-ran the test.sh which deleted and recreated the Pods. |
| Comment by Faseela K [ 18/Dec/18 ] |
|
ankit.ericsson : Ankit did we not have a fix for this? Is it available in master? |