-
Type: Bug
-
Status: Resolved (View Workflow)
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 2.3.0
-
Fix Version/s: 2.3.0
-
Component/s: None
-
Labels:None
If json file uses the short notation for IPV6 address (i.e fdfd:fd60:1300:400:8f1:ea1f::221), we see the issue.
If json file uses the full notation for IPv6 address (i.e fdfd:fd60:1300:400:8f1:ea1f:0:221) , connectivity works fine.
The issue is that device ID is fdfd:fd60:1300:400:8f1:ea1f::221 whereas ip is fdfd:fd60:1300:400:8f1:ea1f:0:221. NetconfDeviceInfo object saves deviceId same as ip and tries NetconfSessionMinaImpl tries to find driver for this deviceId but fails to find it since netcfg config is saved with fdfd:fd60:1300:400:8f1:ea1f::221 as deviceId