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

Type field to select DCAE_INVERNTORY_BLUEPRINT has disappered in SDC Service Composition panel to create an Artifact

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Medium Medium
    • None
    • Frankfurt Release
    • None
    • None

      We have deployed ONAP with Frankfurt build recently (18-11-20) and started using this for control loop design and deployment for vFWCL use case.

      Usually while adding an artifact to the service under deployment artifacts in SDC Service Composition panel where user has to fill the details in 4 mandatory fields listed below to create an Artifact

      1. Upload File - to upload artifact file
      2. Artifact Label - to name the artifact
      3. Description - to describe the artifact
      4. Type - List of blueprints type to be selected (ex: DCAE_INVERNTORY_BLUEPRINT)

      We have been creating DACE artifacts by updating all those fields, but all of a sudden we noticed that the Type* drop down box has disappeared in the SDC Service Composition panel (attached the screenshot) and hence unable to create an artifact now.

      Previously we were seeing this Type* drop down box in the same setup (running Frankfurt) to select DCAE_INVERNTORY_BLUEPRINT as a type and able to create an artifact (attached the screenshot). Suddenly it disappeared and it is not allowed to add artifacts.

      All the SDC pods are in the same state as earlier and we did not change anything.
      We are not sure whether it is a known issue or something broken here, so filing this bug.

      Please find the attached screenshots and SDC pods status below

      SDC pods current status:

        #kubectl get pods -n onap | grep sdc
       dev-cds-sdc-listener-6f4cf56d69-mjcdt 1/1 Running 0 8d
       dev-sdc-be-54c4764646-zv22j 2/2 Running 0 8d
       dev-sdc-be-config-backend-6n8jj 0/1 Completed 0 8d
       dev-sdc-be-config-backend-mrtcq 0/1 Init:Error 0 8d
       dev-sdc-cs-0 1/1 Running 0 8d
       dev-sdc-cs-config-cassandra-g9djw 0/1 Completed 0 8d
       dev-sdc-dcae-be-95dcd7ccf-7vgxt 2/2 Running 0 8d
       dev-sdc-dcae-be-tools-mmb6s 0/1 Init:Error 0 8d
       dev-sdc-dcae-be-tools-wsmw4 0/1 Completed 0 8d
       dev-sdc-dcae-be-tools-wz82s 0/1 Init:Error 0 8d
       dev-sdc-dcae-be-tools-xzx5q 0/1 Init:Error 0 8d
       dev-sdc-dcae-dt-6c8568db54-ldj6q 2/2 Running 0 8d
       dev-sdc-dcae-fe-66894f8765-ktdpt 2/2 Running 0 8d
       dev-sdc-dcae-tosca-lab-59d6f8b74f-m42pp 2/2 Running 0 8d
       dev-sdc-fe-5d6fdfdf96-hp2nw 2/2 Running 0 8d
       dev-sdc-onboarding-be-679c4df66c-7n2dq 2/2 Running 0 8d
       dev-sdc-onboarding-be-cassandra-init-dxvh8 0/1 Completed 0 8d
       dev-sdc-wfd-be-65df5bbd4f-7shxp 1/1 Running 0 8d
       dev-sdc-wfd-be-workflow-init-vmhvx 0/1 Completed 0 8d
       dev-sdc-wfd-fe-54f8596994-rj97v 2/2 Running 0 8d
       dev-so-sdc-controller-747f4485f9-2w5vr 2/2 Running 0 8d
      

       

       

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

              Created:
              Updated:
              Resolved: