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

SO-Mariadb: 'VNF_RESOURCE_CUSTOMIZATION' DB update bug when service is distributed.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: High High
    • None
    • Casablanca Release, Dublin Release
    • None

      When I distribute the service from SDC, there is an error updating 'VNF_RESOURCE_CUSTOMIZATION' table when I declare inputs from the service template. 

      In the table, we can see 'get_input' is not substituted to '${value}|' in some entries. 

      {\"nf_naming\":\"true\",\"multi_stage_design\":\"false\",\"carrierethcep0_service-interface-point\":\"carrierethcepa_carrierethcep0_service-interface-point|\",\"carrierethcep0_s-vlan-id-list\":\"{\\"get_input\\":\\"carrierethcepa_carrierethcep0_s-vlan-id-list\\"}\",\"availability_zone_max_count\":\"1\",\"carrierethcep0_ce-vlan-id-list-and-untag-vlan-id\":{color:#FF0000}"{\\"get_input\\":\\"carrierethcepa_carrierethcep0_ce-vlan-id-list-and-untag-vlan-id\\"}\",\"carrierethcep0_ingress-bwp-flow\":\"carrierethcepa_carrierethcep0_ingress-bwp-flow|\",\"carrierethcep0_layer-protocol-name\":\"carrierethcepa_carrierethcep0_layer-protocol-name|\",\"carrierethcep0_uuid\":\"carrierethcepa_carrierethcep0_uuid|\"}

       

      Since these values, the BPMN process makes error when I send the createcustomE2EserviceInstance request to SO. Specifically, it makes an error in 'Decompose Service' process when it reads the resource data from DB.

      I manually updated the DB  to '{\\\"nf_naming\\\":\\\"true\\\",\\\"multi_stage_design\\\":\\\"false\\\",\\\"carrierethcep0_service-interface-point\\\":\\\"carrierethcepz_carrierethcep0_service-interface-point|\\\",\\\"carrierethcep0_s-vlan-id-list\\\":\\\"carrierethcepz_carrierethcep0_s-vlan-id-list|\\\",\\\"availability_zone_max_count\\\":\\\"1\\\",\\\"carrierethcep0_ce-vlan-id-list-and-untag-vlan-id\\\":\\\"carrierethcepz_carrierethcep0_ce-vlan-id-list-and-untag-vlan-id|\\\",\\\"carrierethcep0_ingress-bwp-flow\\\":\\\"carrierethcepz_carrierethcep0_ingress-bwp-flow|\\\",\\\"carrierethcep0_layer-protocol-name\\\":\\\"carrierethcepz_carrierethcep0_layer-protocol-name|\\\",\\\"carrierethcep0_uuid\\\":\\\"carrierethcepz_carrierethcep0_uuid|\\\"}' 

      and it works fine. 

      There is an issue in service distribution process obviously

            msyoon msyoon
            msyoon msyoon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: