Get DRY-RUN/Commit ERROR  "validation failed : '_ncs_XmlTag' object is not subscriptable : undefined" after changing HOP-TYPE from strict to loose for a RSVP-TE with explicit path: 1. Use CNC provisioning UI to successfully create a PCC-init RSVP-TE. The headend is a XE device (ASR-907) and tailend is a XRV9K 7.3.2 device. The RSVP-TE is created with explicit path with numbered-node-hop and hop-type is 'strict'2. Go back to CNC provisioning UI to edit the same RSVP-TE. Change hop-type from 'strict' to 'loose' and try to do dry-run and commit.3. Either doing Dry-Run or Commit, it ends up with popup error - "validation failed : '_ncs_XmlTag' object is not subscriptable : undefined" 4. Below is the RSVP-TE payload that's successfully provisioned { "ietf-te:tunnel": {  "name": "RSVP-907-112",  "source": "41.41.41.41",  "head-end": "JSS-ASR-907",  "tail-end": "xrv9k-732-112",  "identifier": 4112,  "description": "XE41 to XR112",  "destination": "112.112.112.112",  "hold-priority": 3,  "setup-priority": 3,  "traffic-steering": {   "autoroute": {    "announce": {     "metric": {      "constant": 2147483647     }    },    "destination": [     {      "address": "111.111.111.111"     }    ]   }  },  "p2p-primary-paths": {   "p2p-primary-path": [    {     "name": "path-explicit-41-112",     "path-computation-method": "ietf-te-types:path-explicitly-defined",     "explicit-route-objects-always": {      "route-object-include-exclude": [       {        "index": 1,        "numbered-node-hop": {         "node-id": "115.115.115.115",         "hop-type": "strict"        }       },       {        "index": 2,        "numbered-node-hop": {         "node-id": "116.116.116.116",         "hop-type": "strict"        }       },       {        "index": 3,        "numbered-node-hop": {         "node-id": "114.114.114.114",         "hop-type": "strict"        }       },       {        "index": 4,        "numbered-node-hop": {         "node-id": "112.112.112.112",         "hop-type": "strict"        }       }      ]     }    }   ]  } }}
Hi Jen-Shue, Was able to reproduce the issue. Please file a CDETs.Thanks,RegiIssue is being tracked by CDETs: 