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

SDC-BE pod started but it's responding with 503 HTTP code

XMLWordPrintable

      We are trying to start ONAP on GoogleCloud VM/Rancher/Kubernetes. We are using cd.sh script provided in https://jira.onap.org/browse/OOM-716 (the latest version: [^cd.sh).] 

      The problem is with SDC-BE pod. It is shown in Kubernetes that it's working fine as port 8443 is open but when we try to get this port or 8080 via http we got 503 Service Unavailable. Few other pods like dev-sdc-be-config-backend, dev-sdc-fe are waiting for this service to respond properly but it's not doing that. We have reviewed the logs from sdc-be and there is nothing interesting at list from ERROR point of few. Seems that the service is not able to respond properly.

       

      Seems that the rest pods are waiting for sdc-be to create web context /sdc2 but this is not happening!

        1. jetty.tar.gz
          246 kB
        2. SDC-BE.7z
          8.13 MB
        3. sdc-be.txt
          225 kB
        4. sdc-be-pod-configuration.yaml
          12 kB

            ml636r ml636r
            kapalkat kapalkat
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: