[TRNSPRTPCE-251] Netconf connection failing when using multiple netconf client on a single netconf server Created: 24/Apr/20  Updated: 16/Jan/24

Status: Open
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Christophe BETOULE Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File EditConfig.py    
Issue Links:
Duplicate
duplicates TRNSPRTPCE-249 Device listener fails to read Honeyno... Open
Priority: Normal

 Description   

This issue raised only for this specific configuration of TransportPCE can be reproduced using change 88597(device listener implementation, OnNotificationChange) :

  • Start one instance of TransportPCE controller
  • Start for example one instance of Honeynode device 1.2.1 with oper-ROADMA-full configuration (which is an openroadm device implementing an odl netconf server)
  • Connect TransportPCE controller to this instace of Honeynode device

Once the device is registered and the listeners are created, perform an “edit-config” on this Honeynode using either the attached python script or any Netconf browser application.

It generates a notification from the Honeynode that is correctly catched by the TransportPCE controller, triggering the “onChangeNotification” method of the DeviceListener class of TransportPCE.

But, it makes an issue within the getDeviceTransaction method implemented in the DeviceTransactionManagerImpl class, leading to a netconf disconnection after a timeout.

 


Generated at Wed Feb 07 20:42:37 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.