Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-2799

so-bpmn-infra pod stuck in init state

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • Honolulu Release, Istanbul Release
    • readiness
    • None
    • Hide

      SUMMARY

      restart of so-bpmn-infra pod in a long term deployed ONAP instance results in pod being stuck in init state forever

      OS / ENVIRONMENT

      • Kubernetes version:
        Client Version: v1.19.9
        Server Version: v1.19.9
      • Helm version:
        v3.5.2+g167aac7
      • Kubernetes mode of installation:
        rke version v1.2.7

      OOM VERSION

      Honolulu 8.0.1

      commit be3baadbcf424fab7c1dd1916a46558a6e9daeb1

      STEPS TO REPRODUCE

      After successful deployment of ONAP

      delete the completed pod corresponding to so-mariadb-config-job emulating garbage collector deleting long term completed pods for freeing up resources

      delete so-bpmn-infra pod, which leads to recreating the pod again but it is stuck in init state forever as it keeps looking for pod corresponding to so-mariadb-config-job which is never created again as job is already completed successfully. 

      EXPECTED RESULTS

      so-bpmn-infra pod is stuck in init state

      ACTUAL RESULTS

      so-bpmn-infra should return back to running state

      Show
      SUMMARY restart of so-bpmn-infra pod in a long term deployed ONAP instance results in pod being stuck in init state forever OS / ENVIRONMENT Kubernetes version: Client Version: v1.19.9 Server Version: v1.19.9 Helm version: v3.5.2+g167aac7 Kubernetes mode of installation: rke version v1.2.7 OOM VERSION Honolulu 8.0.1 commit be3baadbcf424fab7c1dd1916a46558a6e9daeb1 STEPS TO REPRODUCE After successful deployment of ONAP delete the completed pod corresponding to so-mariadb-config-job emulating garbage collector deleting long term completed pods for freeing up resources delete so-bpmn-infra pod, which leads to recreating the pod again but it is stuck in init state forever as it keeps looking for pod corresponding to so-mariadb-config-job which is never created again as job is already completed successfully.  EXPECTED RESULTS so-bpmn-infra pod is stuck in init state ACTUAL RESULTS so-bpmn-infra should return back to running state

          prabhjot prabhjot
          prabhjot prabhjot
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

            Created:
            Updated:
            Resolved: