Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-3391

Service with PNF distribution error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: High High
    • Honolulu Release
    • Guilin Release
    • None
    • None

      For service with PNF resource there is a distribution error for a few ONAP components (A&AI and CLAMP). From logs I can see that PNF node_template has invalid type (same log on both components):

      2020-11-26 14:58:38.038 [pool-3-thread-10] ERROR org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory - ####################################################################################################
      2020-11-26 14:58:38.039 [pool-3-thread-10] ERROR org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory - ToscaTemplate - verifyTemplate - 1 Parsing Critical occurred...
      2020-11-26 14:58:38.039 [pool-3-thread-10] ERROR org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory - JTosca Exception [JE136]: InvalidTypeError: "org.openecomp.resource.pnf.PnfRu8" is not a valid type. CSAR name - /tmp/sdc-controllers/sdc-controller/service-ServicePnfRu8-csar.csar
      2020-11-26 14:58:38.039 [pool-3-thread-10] ERROR org.onap.clamp.clds.sdc.controller.SdcSingleController - SdcArtifactInstallerException exception caught during the notification processing
      org.onap.sdc.tosca.parser.exceptions.SdcToscaParserException: Error: CSAR file bad format. Check the log for details.
      at org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory.throwSdcToscaParserException(SdcToscaParserFactory.java:197)
      at org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory.init(SdcToscaParserFactory.java:90)
      at org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory.getSdcCsarHelper(SdcToscaParserFactory.java:61)
      at org.onap.clamp.clds.sdc.controller.installer.CsarHandler.save(CsarHandler.java:120)
      at org.onap.clamp.clds.sdc.controller.SdcSingleController.treatNotification(SdcSingleController.java:271)
      at org.onap.clamp.clds.sdc.controller.SdcSingleController$SdcNotificationCallBack.activateCallback(SdcSingleController.java:101)
      at org.onap.sdc.impl.NotificationConsumer.run(NotificationConsumer.java:71)
      at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
      at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
      at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.base/java.lang.Thread.run(Unknown Source)
      2020-11-26 14:58:38.040 [pool-3-thread-10] INFO org.onap.clamp.clds.sdc.controller.SdcSingleController - Sending DEPLOY(DEPLOY_ERROR) notification to SDC for artifact:/sdc/v1/catalog/services/ServicePnfRu8/1.0/artifacts/service-ServicePnfRu8-csar.csar(Error: CSAR file bad format. Check the log for details.)

       

      Service CSAR attached

        1. Capture1.PNG
          Capture1.PNG
          37 kB
        2. image-2021-02-05-09-31-00-637.png
          image-2021-02-05-09-31-00-637.png
          373 kB
        3. resource-Newpnf-csar.csar
          67 kB
        4. screenshot-1.png
          screenshot-1.png
          104 kB
        5. screenshot-2.png
          screenshot-2.png
          102 kB
        6. screenshot-3.png
          screenshot-3.png
          100 kB
        7. screenshot-4.png
          screenshot-4.png
          28 kB
        8. screenshot-6.png
          screenshot-6.png
          55 kB
        9. sdc_issue_artifacts.zip
          24 kB
        10. service-Newservicepnf-csar.csar
          68 kB
        11. service-ServicePnfRu8-csar.csar
          66 kB
        12. service-ServicePnfRu8-csar-frankfurt.csar
          69 kB

            michaljagiellotmpl michaljagiellotmpl
            michaljagiellotmpl michaljagiellotmpl
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: