[BGPCEP-596] 3node failure due to ConflictingModificationAppliedException Created: 07/Nov/16  Updated: 03/Mar/19  Resolved: 17/Mar/17

Status: Verified
Project: bgpcep
Component/s: PCEP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Vratko Polak Assignee: Claudio David Gasparini
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Blocks
is blocked by BGPCEP-581 Integrate PCEP topology provider with... Verified
External issue ID: 7102

 Description   

This was seen in CSIT Netconf all job, causing a red dot.
See [0] from 2016-11-07 13:16:41,665.
But most all jobs usually pass without triggering this.

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.

[0] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/87/console.log.gz

 Comments   
Comment by Vratko Polak [ 08/Nov/16 ]

A logging improvement [1] shows in Sandbox run [2] that pcep-topology is indeed the node of conflict:

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[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=pcep-topology}

]]]}
17:19:59 at org.opendaylight.controller.cluster.datastore.ShardDataTree.processNextTransaction(ShardDataTree.java:540)

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.

[1] https://git.opendaylight.org/gerrit/48118
[2] https://jenkins.opendaylight.org/sandbox/job/netconf-csit-3node-clustering-all-carbon/5/console

Comment by Claudio David Gasparini [ 17/Mar/17 ]

Logs are seen because of missconfiguration of PCEP, based on the guide.
Running 3 instances with same config.
Nevertheless "issue" has been solved once CSService has been implemented under PCEP.

Generated at Wed Feb 07 19:13:32 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.