Non json formatted notifications being transmitted to CNC: Non json formatted notifications being transmitted to CNC:{ "ietf-restconf:notification": { "eventTime": "2022-03-25T17:29:48.494948+00:00", "tailf-ncs:plan-state-change": {"service": /ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service[vpn-id='0-65008740'],<<--- Missing  enclosing the value "component": "DEVLF1SLR02_23", "state": tailf-ncs:ready, "operation": "modified", "status": "reached" } }}
Hello, Can we please get information on the setup where this error is present. Thank you!What information do you need..?NSO 5.4.4.1CNC 2.xPackages:NAME             VERSION ---------------------------------------alu-sr-cli-8.22        8.22.2  cisco-flat-L2vpn-fp      2.0.0  cisco-flat-L2vpn-fp-internal 2.0.0  cisco-flat-L3vpn-fp      2.0.2  cisco-flat-L3vpn-fp-internal 2.0.4  cisco-ios-cli-6.67      6.67.8  cisco-iosxr-cli-7.33     7.33.20 cisco-iosxr-nc-7.3      7.3.1  cisco-rsvp-te-fp       2.0.1  cisco-sr-te-cfp        2.0.0  cisco-sr-te-cfp-internal   2.0.0  cisco-tsdn-core-fp-common   2.0.0  core-fp-common        1.11.0  core-fp-delete-tag-service  1.0.2  core-fp-plan-notif-generator 1.0.0  custom-template-utils     2.0.5  cw-device-auth        1.0.0  dlm              4.0   flat-l2vpn-multi-vendors   2.0.0  flat-l3vpn-multi-vendors   2.0.0  flat-l3vpn-nokia       2.0.1  ietf-l2vpn-nm         2.0.0  ietf-l3vpn-nm         2.0.5  ietf-te-fp          2.0.0  resource-manager       3.5.4  rsvp-te-multi-vendors     2.0.0  sr-pce            1.0   sr-te-multi-vendors      2.0.0  tailf-hcc           5.0.2 The error appears when we deploy, modify, delete a service in the notification stream to CNC which rejects it as its not a valid JSOn format. Attaching email summary from Liran who helped diagnose the issue. Hello,Thank you for the above info.If possible I would like access to the NSO that has this error so I can run some commands to check the error.If not possible, please attach the payload of this service to this ticket.If you can propose a time during CET business hours I can possibly give you access via a screen share, as this is a customer deployment there is no generic cisco access without customer remote access clients.Any service creation (payload example) seems to trigger the malformed JSON service field in the RESTCONF notification message sent to CNC.Example:{ "ietf-restconf:notification": { "eventTime": "2022-03-25T17:29:48.494948+00:00", "tailf-ncs:plan-state-change": {"service": /ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service[vpn-id='0-65008740'], "component": "DEVLF1SLR02_23", "state": tailf-ncs:ready, "operation": "modified", "status": "reached" } }}The issue in the above format is missing enclosing quotes in: /ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service should be "service": "/ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service"Regards. Hello,Please let us know if 3PM - 4PM CET works for you?Since we are unable to reproduce this issue on our end we would like to g through the steps on the meeting.If thats on Friday yes works well for me.Please can we invite Liran Mendelovich (lmendelo) <lmendelo@cisco.com>, as he was the one that diagnosed the symptoms and knows how to show the error from the CNC side...Thank you - meeting invite has been sent.Hi Ulfat, After further investigation, we have concluded that this is a platform bug with NSO 5.4.4.1. The fix has been included in NSO 5.4.5.2. Please let us know if this bump is okay with you.Attached meeting minutes from 4/1/2022.Can you verify if the fix is also in 5.4.6, there is another work stream that may require is to upgrade to this release and we would like to verify if the same issue is fixed or not in that future release..? Thanks.Hello Ulfat, Yes this fix is present in 5.4.6 and subsequent releases. Also attached verification screenshot. Thank you.Hello, please confirm if this issue/questions is resolved so I may close the ticket. Thank you.I can confirm that upgrading to 5.4.5.2 fixed the issue. You can close the ticket. ThanksGreat - Thank you!Issue was being seen in NSO version 5.4.4.1.Customer has upgraded to NSO version 5.4.5.2 and issue is no longer seen.Resolving ticket.