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

SDC health check failed with 500 Error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • Frankfurt Release
    • None
    • Offline installation of ONAP using offline installer with one Infra and 3 Kubernetes

      Hi Team

      We have deployed onap 'Frankfurt' using offline installer on Kubernetes. While doing robot health check SDC health check is failed except for fe component. On cheking further we found that the config for the pods seem to be failed while they are in running state. For example see below for sdc-dcae-be:

       

      onap-sdc-dcae-be-6c7748cc4c-ppm95 2/2 Running 0 6d18h
      onap-sdc-dcae-be-tools-6tx7x 0/1 Completed 0 6d10h

       

      On checking logs from onap-sdc-dcae-be-tools-6tx7x. I see the below error while on running container onap-sdc-dcae-be-6c7748cc4c-ppm95, I do not see any error:

      Starting VFCMT template deployment
      Arguments:
      ../conf/environment.json
      ../conf/config.json
      Connecting to server host: https://sdc-dcae-be.onap, port: 8444
      SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
      SLF4J: Defaulting to no-operation (NOP) logger implementation
      SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

       

      Pls help to resolve the issue. Thanks

        1. screenshot-1.png
          screenshot-1.png
          60 kB
        2. screenshot-2.png
          screenshot-2.png
          109 kB
        3. sdc_logs.log
          248 kB
        4. sdc-be_20200903.log
          3.80 MB

            Unassigned Unassigned
            devanshu_tyagi devanshu_tyagi
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: