https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/BGPCEP-596 bgpcep <p>This was seen in CSIT Netconf <del>all</del> job, causing a red dot.<br/> See <span class="error">&#91;0&#93;</span> from 2016-11-07 13:16:41,665.<br/> But most <del>all</del> jobs usually pass without triggering this.</p> <p>Possibly, a push of 39-pcep-provider.xml runs a code block aimed to create an empty pcep-topology, but the code block does not expect other member of cluster (also running the block) to interfere with its transactions.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/87/console.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/87/console.log.gz</a></p> <p>Operating System: All<br/> Platform: All</p> BGPCEP-596

3node failure due to ConflictingModificationAppliedException

Bug Verified Cannot Reproduce Claudio David Gasparini Vratko Polak Mon, 7 Nov 2016 14:26:57 +0000 Sun, 3 Mar 2019 11:49:57 +0000 Fri, 17 Mar 2017 07:12:49 +0000 Bugzilla Migration Bugzilla Migration PCEP 0 2 <p>A logging improvement <span class="error">&#91;1&#93;</span> shows in Sandbox run <span class="error">&#91;2&#93;</span> that pcep-topology is indeed the node of conflict:</p> <p>17:19:59 OptimisticLockFailedException{message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., 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 at path /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[</p> {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=pcep-topology} <p>]]]}<br/> 17:19:59 at org.opendaylight.controller.cluster.datastore.ShardDataTree.processNextTransaction(ShardDataTree.java:540)</p> <p>I have seen one RelEng run which does not mention 39-pcep-provider.xml, so this Bug is probably enabled by some other configfile, 32-pcep.xml maybe.</p> <p><span class="error">&#91;1&#93;</span> <a href="https://git.opendaylight.org/gerrit/48118" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/48118</a><br/> <span class="error">&#91;2&#93;</span> <a href="https://jenkins.opendaylight.org/sandbox/job/netconf-csit-3node-clustering-all-carbon/5/console" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/sandbox/job/netconf-csit-3node-clustering-all-carbon/5/console</a></p> <p>Logs are seen because of missconfiguration of PCEP, based on the guide.<br/> Running 3 instances with same config.<br/> Nevertheless "issue" has been solved once CSService has been implemented under PCEP.</p> Blocks BGPCEP-581 Development External issue ID 7102 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02d9j: