get_schema API issue on NSO M3 version: get_schema API issue on NSO M3 version.Request{"params": {"levels": -1,"insert_values": true,"stop_on_list": true,"path": "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{TEST1}/vpn-nodes/vpn-node{TB3-P-BOTTOMLEFT}","evaluate_when_entries": true,"th": 5},"jsonrpc": "2.0","id": 102,"method": "get_schema"}Response{"jsonrpc": "2.0","error": {"type": "session.invalid_sessionid","code": -32000,"message": "Invalid sessionid"},"id": 102}
Hi Demeke,I tested in my local and the API seems to be working and getting the result correctly. From the message it seems like the session-id that you are using is invalid. Please use the "login" and "new_trans" API to get the session-id and transaction-id and then run this command with those id.Let us know your NSO setup details for us to check further in case the above does not work.Thanks,NikhilHi Nikhil,I still see this issue admin/Ovatest123@Try to create l2vpn services and when you add the vpn-node you will see the issue.Let me know if you want a webex session also.Thanks,Demeke.Hi Demeke,The above are CNC UI details. Can you help us with the NSO console server and login details?Please message me on teams if you want to have a session to discuss this.Thanks, NikhilHi Nikhil,Please find the NSO setup info. 10.22.179.181ubuntudoc/ubuntudocThanks,Demeke.Hi Demeke,This looks like a platform issue with the IETF L2NM model. We have raised a RT with the NSO platform team and will let you know once we hear anything from them.As a workaround, the get_schema request with "insert_values" = "false" can be used from CNC side. We have tested the same and it seems to be working fine. Below is the sample request:Request{"params": {"levels": -1,"insert_values": false,"stop_on_list": true,"path": "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{TEST1}/vpn-nodes/vpn-node{TB3-P-BOTTOMLEFT}","evaluate_when_entries": true,"th": 5},"jsonrpc": "2.0","id": 102,"method": "get_schema"}Thanks,NikhilHi Nikhil,The suggested workaround works but it breaks CNC Prov-UI dynamic implementation and we are waiting for the official fix.Thanks,Demeke.Hi Demeke,We have already opened a case with the platform team for this issue. Will update you as soon as we hear from them.Thanks,NikhilHi Nikhil,We have tried the workaround to use the insert_values=false, and that cause issue in the subsequent get_schema API. And we have looked the get_elem API and that also does not help for our use case. In Prov-UI we use get_schema api and parse the data to show the panel view. Therefore the workaround is not working for our use-case and looking for the fix.This is a related ticketThanks,Demeke. Hi Demeke,The below RT raised for this issue with NSO team has been fixed:The change will be included in thebelow and later versions:nso-5.5.9 (31-Jan-2023)nso-5.6.11nso-5.7.9 (24-Jan-2023)nso-5.8.7nso-6.0.1.1nso-6.0.2 (17-Jan-2023)nso-6.1 (13-Apr-2023)Thanks,NikhilRT raised for this issue was fixed by the NSO team and hence the issue is resolved.