-
Bug
-
Resolution: Won't Do
-
Medium
-
Casablanca Release
-
None
-
OOM (latest)
xenial
After cleaning whole environment via
root@oom-beijing-master-xenial:~# helm delete dev --purge
release "dev" deleted
DCAE pods are still running ...
root@oom-beijing-master-xenial:~# kubectl get pods --namespace=onap
NAME READY STATUS RESTARTS AGE
dep-config-binding-service-764669577b-xpxwg 2/2 Running 0 5h
dep-dcae-tca-analytics-5c69d49d98-445s9 2/2 Running 0 5h
dep-dcae-ves-collector-84d5bc874f-sfbvm 2/2 Running 0 5h
dep-deployment-handler-6cd5d48c65-f5m6q 2/2 Running 0 5h
dep-policy-handler-7ddb988dc6-bflmj 2/2 Running 0 5h
dep-pstg-write-787c4bb65b-bkslf 1/1 Running 0 5h
- blocks
-
LOG-898 ONAP Deployment Resiliency changes to deploy without POD failures
- Closed
-
TSC-25 Task Force to implement CD (Continuous Deployment)
- Closed
-
DCAEGEN2-1067 Deploying DCAEGEN2 late in a sequenced deployment will cause the secondary cloudify orchestration pods DEP* to fail
- Closed
-
DCAEGEN2-1068 DCAEGEN2 failed redeployment leaves cloudify orchestrated dev-dcae namespace pods up
- Closed
-
LOG-326 CD: OOM automated deployment script
- Closed
- is blocked by
-
OOM-508 Add support to DCAEGEN2
- Closed
-
OOM-1586 Add --force --grace-period=0 delete pod capability to cd.sh script
- Closed
- relates to
-
OOM-1580 HELM undeploy may hang on Terminating pods that need a --purge
- Closed
-
OOM-1586 Add --force --grace-period=0 delete pod capability to cd.sh script
- Closed
-
LOG-918 LOG Pipeline addition for DCAE secondary Cloudify orchestration pods
- Closed
- mentioned in
-
Page Loading...