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

SO 1.5.0-STAGING-latest containers fail liveness probe

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Highest Highest
    • El Alto Release
    • El Alto Release
    • integration-stagig-daily

      Occurs in Azure as well.

       

      Three (3) pods failing to connect in health check

       sdc-handler, openstack-adapter, vnfm-adapter

       

      Warning Unhealthy 46s (x50 over 3h29m) kubelet, staging-k8s-08 Liveness probe failed: Get http://10.42.4.79:8087/manage/health: dial tcp 10.42.4.79:8087: connect: connection refused

       

      ==============================================================================
      Basic SO Health Check | FAIL |
      Test timeout 20 seconds exceeded.
      ------------------------------------------------------------------------------

        1. image_7.GIF
          image_7.GIF
          69 kB
        2. image (8).png
          image (8).png
          72 kB

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

              Created:
              Updated:
              Resolved: