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

CreateTunnelXConn SDNC assign request needs fix

XMLWordPrintable

      The TunnelXConn allotted resource assign request to SDNC caused an error in SDNC. The message from the SDNC side is below:

      failed on query / put to AAI
      2017-11-04 02:37:18,538 | DEBUG | tp1179980033-544 | AAIService | 300 - org.openecomp.sdnc.sli.aai - 0.1.0 | resolveTerm: term is allotted-resource.id 2017-11-04 02:37:18,538 | DEBUG | tp1179980033-544 | AAIService | 300 - org.openecomp.sdnc.sli.aai - 0.1.0 | resolveTerm: term is $tmp.ar.allotted-resource-id 2017-11-04 02:37:18,539 | INFO | tp1179980033-544 | AAIService | 300 - org.openecomp.sdnc.sli.aai - 0.1.0 | Input - id : 2d619a10-f1e5-45f0-97f9-49fee0b7c420 2017-11-04 02:37:18,539 | INFO | tp1179980033-544 | AAIService | 300 - org.openecomp.sdnc.sli.aai - 0.1.0 | Input - service-type : null 2017-11-04 02:37:18,539 | INFO | tp1179980033-544 | AAIService | 300 - org.openecomp.sdnc.sli.aai - 0.1.0 | Input - global-customer-id : null 2017-11-04 02:37:18,539 | INFO | tp1179980033-544 | AAIService | 300 - org.openecomp.sdnc.sli.aai - 0.1.0 | Input - service-instance-id : null

       

      The url that SDNC used to access AAI is failing:

      2017-11-04 02:37:18,540 | INFO | tp1179980033-544 | AAIService | 300 - org.openecomp.sdnc.sli.aai - 0.1.0 | Request URL : https://aai.api.simpledemo.openecomp.org:8443/aai/v11/business/customers/customer/null/service-subscriptions/service-subscription/null/service-instances/service-instance/null/allotted-resources/allotted-resource/2d619a10-f1e5-45f0-97f9-49fee0b7c420

       

      SDNC parsed the SO request and got a few blank fields:

      getServiceInformation=ServiceInformation{getGlobalCustomerId=, getOnapModelInformation=OnapModelInformation{augmentations={}}, getServiceId=, getServiceInstanceId=a8aa6fef-fbe5-4d13-8544-6514cfca8233, getSubscriberName=, getSubscriptionServiceType=, augmentations={}

       

      I'm attaching two request for your reference:

      • Service assign request from SO to SDNC. This one succeeded. It has more information in the <service-information> section.
      • TunnelXConn assign request from SO to SDNC. This one led to the above errors. 

       

       

            kxi kxi
            kxi kxi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: