[GENIUS-207] UpgradeUtils OptimisticLockFailedException Created: 30/Aug/18 Updated: 10/Sep/18 Resolved: 10/Sep/18 |
|
| Status: | Resolved |
| Project: | genius |
| Component/s: | mdsalutils |
| Affects Version/s: | None |
| Fix Version/s: | Neon |
| Type: | Bug | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Michael Vorburger |
| Resolution: | Done | Votes: | 0 |
| Labels: | csit:3node | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Clustering Stability |
| Description |
|
Forking off the OLFE (OptimisticLockFailedException) in UpgradeUtils from 2018-08-13T07:29:52,155 | ERROR | opendaylight-cluster-data-notification-dispatcher-76 | UpgradeUtils | 266 - org.opendaylight.genius.mdsalutil-impl - 0.4.4 | Unable to update UpgradeState
java.util.concurrent.ExecutionException: OptimisticLockFailedException{message=Optimistic lock failed for path /(urn:opendaylight:serviceutils:upgrade?revision=2018-07-02)upgrade-config, errorList=[RpcError [message=Optimistic lock failed for path /(urn:opendaylight:serviceutils:upgrade?revision=2018-07-02)upgrade-config, severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was replaced by other transaction.]]}
Caused by: org.opendaylight.controller.md.sal.common.api.data.OptimisticLockFailedException: Optimistic lock failed for path /(urn:opendaylight:serviceutils:upgrade?revision=2018-07-02)upgrade-config
Caused by: org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was replaced by other transaction.
The review discussion in https://git.opendaylight.org/gerrit/#/c/75535/ is an interesting clustering related discussion. |
| Comments |
| Comment by Michael Vorburger [ 30/Aug/18 ] |
|
Once we have agreed on the right solution for this specific bug, still under discussion, then IMHO it would be worthwhile to turn it into general developer documentation - somewhere - tpantelis, skitt any thoughts where such a doc would have to go? |
| Comment by Michael Vorburger [ 10/Sep/18 ] |
|
This problem (from Fixed in Neon only; not critical enough for Fluorine back-port IMHO, as ERROR log only appears x1 during start up. |