RON Failed plan "status-code-detail" has device name in incorrect key: Generally when we have a failed plan for a service, there is a section called "status-code-details" - and it has per device information about the error. In this section the name of the device is generally in "impacted-device" - but for a failed RON plan the name of the device is in "name".Because we have a screen in CNC that relies on this information - our logic is breaking because of changed key. Is this something that can be corrected?Attached: JSON representation of RON failed plan showing the name of the device as "name"Attached: CNC screen which relies on this JSON - with empty device name - because it expected "impacted-device"
Hi Mukul - could you please provide the steps to reproduce and also the NSO payload for which you landed into the above issue.Here is the NSO payload - { "cisco-ron-cfp:ron-ml": {  "mode": "transponder",  "name": "BLUE_OLS_BTMLFT_TPRT_400_TR",  "dac-rate": "1x1",  "bandwidth": "400",  "end-point": [   {    "end-point-device": "P-BOTTOMLEFT",    "terminal-device-packet": {     "interface": [      {       "index": 0,       "ip-address": {        "v4": "20.20.10.46/30"       }      }     ]    },    "terminal-device-optical": {     "line-port": "0/0/0/1",     "transmit-power": -90    }   },   {    "end-point-device": "P-TOPRIGHT",    "terminal-device-packet": {     "interface": [      {       "index": 0,       "ip-address": {        "v4": "20.20.10.45/30"       }      }     ]    },    "terminal-device-optical": {     "line-port": "0/0/0/1",     "transmit-power": -90    }   }  ],  "grid-type": "100mhz-grid",  "circuit-id": "2",  "ols-domain": {   "service-state": "UNLOCKED"  } }}Steps to reproduce are just execute the payload - and if the plan fails - then the failed plan doesn't match the regular TSDN CFP schema.I would just say that we should see if the failed plan construction differs from the TSDN CFP failed plan.Because I don't have absolute steps to make the service fail.Here is that section from a sample L3vpn failed plan with key as "impacted device"So did you send commit-queue parameters when executing the RON payload?These are being created using HTTP PATCH using CNC RESTCONF - which should be a wrapper over NSO restconf on URLWe're not specifying commit-queue parameters anywhere.Hey Mukul,I tried reproducing using the above payload but not able to fail the plan. Could you please provide the details of your nso server or share logs.Please use NSO as readonly. It is at admin / Public1234! Here you can find the service - BLUE_OLS_BTMLFT_TPRT_400_TRI also attached screenshot of the plan from both RON-ML and a normal L3VPN - one has impacted device in NSO.. one doesn'tSSH: nso552/Public1234!!Please use readonly. I don't own this NSOHi Mukul,Thanks for providing the server but its lot of information and was not so useful. We were looking at way to reproduce the issue as with the payload we couldnt reproduce. Anyhow I have opened an internal Jira ticket() for further analysis and fixing the issue in later build. I will go ahead and close this support ticket. Let me know if you have any doubts.HI Mukul, I am closing this ticket as i have opened an internal ticket to address this issue. Kindly see the comments section for more details.Thanks Mohit. I'm not able to view the other JIRA ticket. Please keep me updated with the status of the issue.