[TRNSPRTPCE-443] Otn topology creation fails for Xponder nodes Created: 21/Apr/21 Updated: 18/Jun/21 Resolved: 04/Jun/21 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Silicon |
| Type: | Bug | Priority: | High |
| Reporter: | Shweta Vachhani | Assignee: | Shweta Vachhani |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 day | ||
| Original Estimate: | Not Specified | ||
| Description |
|
10:06:58.271 ERROR [opendaylight-cluster-data-notification-dispatcher-51] member-1-shard-topology-operational: Error notifying listener org.opendaylight.mdsal.binding.dom.adapter.BindingDOMDataTreeChangeListenerAdapter@6c0050c8
While creating OTN topology, supported interface capability between port mapping and network model are using same revision and convertSupIfCapa is not needed. |
| Comments |
| Comment by Gilles Thouenon [ 23/Apr/21 ] |
|
Yes indeed, this type conversion should not be necessary in topology module. After analysis, it seems that the cast performed in PortMappingVersion221 was not effective, and a bad type for SupportedIfCapabilities were propagated towards topology modules. It's much better to manage this conversion (when necessary) at the portmapping level and manage only a single type of revision for SupportedIfCapabilities in the rest of TransportPCE code. |