Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-4109

SDNC calls fail with the new ODL version (chlorine)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: High High
    • London Release
    • London Release

      In the SDNC patch for London (https://gerrit.onap.org/r/c/oom/+/134393)
      the SO-BPMN-INFRA topoligy calls to SDNC fail:

      2023-05-26T22:42:00.210Z|c618879b-f5dd-4ecd-9780-af3ad7bb1875|camundaTaskExecutor-3|SDNC||Unknown-Target-Entity|http://sdnc-oam.onap:8282/rests/operations/GENERIC-RESOURCE-API:service-topology-operation/|DEBUG|500||Response body: {
  "errors": {
    "error": [
      {
        "error-tag": "malformed-message",
        "error-info": "Identifier may not be empty",
        "error-message": "Invalid path 'GENERIC-RESOURCE-API:service-topology-operation/' at offset 48",
        "error-type": "protocol"
      }
    ]
  }
}

      This is caused by pending "/" in the rest calls, as Alexander found out:

      I could reproduce this issue: Rest path with tailing '/' causes the error.
      'http://sdnc-oam.onap:8282/rests/operations/GENERIC-RESOURCE-API:service-topology-operation/'
      should be:
      'http://sdnc-oam.onap:8282/rests/operations/GENERIC-RESOURCE-API:service-topology-operation'
      Most likely all other requests might be changed as well.

      I assume a fix here should work:
      https://git.onap.org/so/tree/so-sdn-clients/src/main/java/org/onap/so/client/sdnc/SDNCClient.java#n54

            andreasgeissler Andreas Geissler
            andreasgeissler Andreas Geissler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: