cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
979
Views
0
Helpful
1
Replies

JSON Formatting Error from NSO

beasleyjon
Level 1
Level 1

Hi,

We're using NSO 4.7 with Commit Queues.


When posting a request to NSO we get the following response:

 

{
    "commit-queue": {
        "id": "1626889483600",
        "status": "failed""failed-device": [
            {
                "name": "asr9006a",
                "reason":"External error in the NED implementation for device asr9006a: Wed Jul 21 17:44:48.039 UTC
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted.
 !! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface GigabitEthernet0/3/0/8.2967
 service-policy output SIGMA20-39a895e62df8414e930b103e72e53b66-2-1ST-LEVEL-EGRESS shared-policy-instance a9aaf134ddbb4eeba9e63bc430e9ca80
!!% 'policy-lib' detected the 'warning' condition 'Policy-map not found'
!
end"}]}}


We're aware this due to an issue with our configuration templates. However, the problem we're facing is that the returned JSON is badly formatted which causes our JSON parser (which deserialises the response from NSO) to throw an exception.

The issue is with this line:

        "status": "failed""failed-device": [

The JSON is invalid because of the double "" so this appears to be a bug.

Is there any workaround available for this from within NSO to return valid JSON?

 

thanks

1 Reply 1

Alex Stevenson
Cisco Employee
Cisco Employee

 

Have you tried converting the JSON object into a string and then replacing the "", followed by converting it back into a JSON object?