Uploaded image for project: 'Application Controller'
  1. Application Controller
  2. APPC-1830

APPC healthcheck failing on master

XMLWordPrintable

      The APPC robot healthcheck is nowis failing frequently in gates.

      Either an issue on the robot tests (not adapted to an appc update or env update) or in Appc (1 pod 1/2 and staefulset not completed)

      On a recent gating

      no issue with the pods/statefulset but also an error when performing the healthcheck test (https://orange-opensource.gitlab.io/lfn/onap/xtesting-onap-view/results/100971-1/infrastructure-healthcheck/k8s/onap-k8s.log)

      onap-appc-appc-0 2/2 Running 0 70m
      onap-appc-appc-ansible-server-0 1/1 Running 0 70m
      onap-appc-appc-cdt-5fdf6cb46d-rs2hh 1/1 Running 0 70m
      onap-appc-appc-db-0 1/1 Running 0 70m
      onap-appc-appc-db-1 1/1 Running 0 69m
      onap-appc-appc-db-2 1/1 Running 0 67m
      onap-appc-appc-dgbuilder-788c4d8576-fxpjl 1/1 Running 0 70m

      statefulset

      onap-appc-appc 1/1 70m
      onap-appc-appc-ansible-server 1/1 70m
      onap-appc-appc-db 3/3 70m

      But error in the robot healthcheck https://orange-opensource.gitlab.io/lfn/onap/xtesting-onap-view/results/100971-1/healthcheck/medium/medium/log.html#s1-t4

       Note on last master chain (https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/jobs/427699462/artifacts/download), no pods in errors but k8s not as healthy as during the gating

      pods

      onap-appc-0 1/2 Running 0 59m
      onap-appc-ansible-server-0 1/1 Running 0 59m
      onap-appc-cdt-c58666456-x96kk 1/1 Running 0 59m
      onap-appc-db-0 1/1 Running 0 59m
      onap-appc-db-1 1/1 Running 0 55m
      onap-appc-db-2 1/1 Running 0 51m
      onap-appc-dgbuilder-7558bb75cd-rdh5f 1/1 Running 0 59m

      statefulsets

      onap-appc 0/1 59m
      onap-appc-ansible-server 1/1 59m
      onap-appc-db 3/3 59m

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

              Created:
              Updated:
              Resolved: