Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-1640

Three Policy pods are in CrashLoopBackOff after ONAP deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Highest Highest
    • Dublin Release
    • Dublin Release
    • None

    • Integration-OOM-Staging-Daily in Intel/Windriver lab

      After ONAP is deployed, three Policy pods are in CrashLoopBackOff. 

       

      root@staging-rancher:~# kubectl -n onap get pod |grep policy-
dev-dcaegen2-dcae-policy-handler-77d7586446-lm7rk 2/2 Running 0 9h
dev-policy-brmsgw-6f79fd65c5-dmng4 1/1 Running 0 63m
dev-policy-drools-0 1/1 Running 0 63m
dev-policy-nexus-6f6fcb6675-c76g5 1/1 Running 0 63m
dev-policy-pap-574cfb9f99-8sqhw 2/2 Running 0 63m
dev-policy-pdp-0 2/2 Running 0 63m
dev-policy-policy-apex-pdp-0 1/1 Running 0 63m
dev-policy-policy-api-56cff95f4b-5fdms 0/1 CrashLoopBackOff 16 63m
dev-policy-policy-distribution-7f66ddfdf5-mn8tf 1/1 Running 0 63m
dev-policy-policy-pap-6cbf65667b-lxm99 0/1 CrashLoopBackOff 16 63m
dev-policy-policy-xacml-pdp-7885f66974-vx2sl 0/1 CrashLoopBackOff 16 63m
dev-policy-policydb-7f56989bf-v5h25 1/1 Running 0 63m 

       

            xuyang11 xuyang11
            xuyang11 xuyang11
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: