[CONTROLLER-1029] Clustering : Killing a PCEP PCC-mock session does not result in the Operational datastore losing the PCEP topology

Tue, 25 Jul 2023 08:24:20 +0000

I am using a build you provided on 14th Friday Nov for clustering testing. distribution-karaf-0.2.1-Helium-SR1 I’ve deployed a 3 node cluster with

system:property shard.persistent ${PERSISTENCE}
PERSISTENT="false"

module-shards.conf, Possible values: "all", every other value will result in single replica
REPLICA="single"

I am creating PCEP sessions using the pcep-pcc-mock tool described here.

https://wiki.opendaylight.org/view/BGP_LS_PCEP:Testing_components#pcep-pcc-mock

java -jar pcep-pcc-mock-0.3.2-SNAPSHOT-executable.jar --log-level DE --local-address 10.25.2.12 --remote-address 10.25.2.9

This creates 1 pcep session.

When I access the REST API at

10.194.126.205:8181/restconf/operational/network-topology:network-topology/topology/pcep-topology-1

I see

{
"topology": [
{
"topology-id": "pcep-topology-1",
"topology-types": {
"network-topology-pcep:topology-pcep": {}
},
"node": [
{
"node-id": "pcc://10.25.2.12",
"network-topology-pcep:path-computation-client": {
"reported-lsp": [
{
"name": "pcc_10.25.2.12_tunnel_1",
"path": [
{
"lsp-id": 1,
"odl-pcep-ietf-stateful07:lsp": {
"plsp-id": 1,
"odl-pcep-ietf-initiated00:create": false,
"remove": false,
"administrative": true,
"delegate": true,
"sync": true,
"operational": "up",
"processing-rule": false,
"tlvs": {
"lsp-identifiers": {
"ipv4":

{ "ipv4-tunnel-endpoint-address": "10.25.2.12", "ipv4-tunnel-sender-address": "10.25.2.12", "ipv4-extended-tunnel-id": "10.25.2.12" }

,
"lsp-id": 1,
"tunnel-id": 1
},
"symbolic-path-name":

{ "path-name": "cGNjXzEwLjI1LjIuMTJfdHVubmVsXzE=" }

},
"ignore": false
},
"ero":

{ "processing-rule": false, "ignore": false }

}
]
}
],
"ip-address": "10.25.2.12"
}
}
]
}
]
}

I kill the pcep-pcc-mock tool , “ctlr +C” and restart it, I see no changes after 600 seconds.