[CONTROLLER-224] Redundant data in RESTCONF Created: 21/Mar/14 Updated: 25/Jul/23 Resolved: 07/Apr/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | restconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Dana Kutenicsova | Assignee: | Tony Tkacik |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| Issue Links: |
|
||||||||
| External issue ID: | 565 | ||||||||
| Priority: | High | ||||||||
| Description |
|
I augment network-topology.yang : grouping topology-pcep-type { } augment "/nt:network-topology/nt:topology/nt:topology-types" { Code to create the container: // Make sure the topology does not exist // Now create the base topology Futures.addCallback(JdkFutureAdapters.listenInPoolThread(t.commit()), new FutureCallback<RpcResult<TransactionStatus>>() { @Override The resulting xml shows two instances of pcep-topology with the same namespace: <topology xmlns="urn:TBD:params:xml:ns:yang:network-topology"> In the code, there is a check for already existing topology and the log file, only shows one success LOG output: TRACE o.o.b.p.t.p.ServerSessionManager - Topology InstanceIdentifier [path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.NetworkTopology, org.opend Almost the same behaviour with example-linkstate-topology: <topology xmlns="urn:TBD:params:xml:ns:yang:network-topology"> 2014-03-21 01:36:53.440 PDT [nioEventLoopGroup-5-6] DEBUG o.o.b.b.t.p.AbstractTopologyBuilder - Initiating topology builder from RIBImpl{} at InstanceIdentifier [path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology[key=TopologyKey [_topologyId=Uri [_value=example-linkstate-topology]]]]] Not sure if RESTCONF issue, or the data is not correctly written/read to/from md-sal, but this did work maybe a week ago (first noticed 03/18). |