[BGPCEP-168] BGP: network-topology does not exist Created: 18/Nov/14  Updated: 03/Mar/19  Resolved: 03/Dec/14

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

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File karaf_20141118.log.xz    
External issue ID: 2398

 Description   

During clustering testing, sometimes the following warning happens:

2014-11-18 11:29:38,365 | WARN | ult-dispatcher-2 | InMemoryDOMDataStore | 225 - org.opendaylight.controller.sal-inmemory-datastore - 1.2.0.SNAPSHOT | Store Tx: member-1-shard-topology-operational-0 Data Precondition failed for /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology.
org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology does not exist. Cannot apply modification to its children.

leading to error and missing BGP topology:

2014-11-18 11:29:38,397 | ERROR | CommitFutures-0 | AbstractTopologyBuilder

265 - org.opendaylight.bgpcep.bgp-topology-provider - 0.4.0.SNAPSHOT Topology
builder for KeyedInstanceIdentifier {targetType=interface org.opendaylight.yang.gen.v 1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology, p ath=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131 021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network .topology.rev131021.network.topology.Topology[key=TopologyKey [_topologyId=Uri [_val ue=example-linkstate-topology-1]]]]}

failed in transaction DOM-CHAIN-1-0
TransactionCommitFailedException

{message=Data did not pass validation., errorList=[R pcError [message=Data did not pass validation., severity=ERROR, errorType=APPLICATIO N, tag=operation-failed, applicationTag=null, info=null, cause=org.opendaylight.yang tools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:TBD:pa rams:xml:ns:yang:network-topology?revision=2013-10-21)network-topology does not exis t. Cannot apply modification to its children.]]}

Notably, this error has never happened when PCEP component starts quickly enough; that may be why this bug was not visible before clustering.
Possibly, the fix could be just to add 'true' as fourth argument, at the end of line 82 of AbstractTopologyBuilder.java

 Comments   
Comment by Vratko Polak [ 18/Nov/14 ]

Attachment karaf_20141118.log.xz has been added with description: Compressed full karaf.log

Comment by Vratko Polak [ 18/Nov/14 ]

I was able to trigger this bug on recent build from master (without clustering) like this:

0. Have an ODL installation where odl-bgpcep-all feature was installed once, so featured congfig files are created; but ODL is currently not started.
1. Delete /data, /cache; edit config files with "pcep" in them to make "required-capabilities", "modules" and "services" empty.
2. Start karaf with BGP speaker present and ODL configured to connect there; feature:install odl-bgpcep-all
3. Examine karaf.log to see "network-topology does not exist".

> Possibly, the fix could be just to add 'true' as fourth argument, at the end
> of line 82 of AbstractTopologyBuilder.java

Now available as https://git.opendaylight.org/gerrit/#/c/12913/ (against master branch of bgpcep repository).

With this patch in, I have repeated the procedure above, and step 3 did not show the error.

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