Uploaded image for project: 'Portal'
  1. Portal
  2. PORTAL-977

Portal-app pod failed to initialize Error code 137

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • Frankfurt Release
    • Portal

    • We have following VMs on Openstack Env:

      • Infra Node(Kubernetes Master)
      • Worker VM1
      • Worker VM2
      • Worker VM3

      ONAP installation done using offline installer.

      Hi Team,

      Recently I faced an issue with Portal-app and some other services, it went to the OOMKilled state with error code 137 after the node restart.

      Earlier to restart, the system was up and running but these services wen down after the Kubernetes worker was restarted.

      [root@infracentos2 ~]# kubectl -n onap get pod -o wide| grep onap-portal-app
      onap-portal-app-5475b4b76d-bt5qr 0/2 Init:OOMKilled 1 80m 10.42.3.31 kubecentos2-3 <none> <none>

      I have checked on the node and there is enough memory available.

      Please help to identify the problem.

            tattasunder tattasunder
            devanshu_tyagi devanshu_tyagi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: