-
Bug
-
Resolution: Not a Bug
-
High
-
El Alto Release
-
None
-
hello,
per default, a node can have no more than 110 pods. Here you have more so you have to deploy using at least two nodes
version: master branch
page: guides/onap-developer/settingup/index
When trying to deploy ONAP El Alto Release some pods keep the status CrashLoopBackOff or Init indefinitely.
General information:
The deployment was made on AWS, single node.
ONAP : El Alto Release
Controller : m5.large
Worker : m5.4xlarge
Kubernetes v1.15.11
Helm v2.14.2
The following pods don't change state
$ kubectl get pods -n onap | grep "CrashLoopBackOff|Error|Init"
| NAME | READY | STATUS | RESTARTS | AGE |
|---|---|---|---|---|
| dev-appc-appc-db-0 | 0/1 | CrashLoopBackOff | 6 | 21h |
| dev-appc-appc-db-1 | 0/1 | CrashLoopBackOff | 7 | 21h |
| dev-appc-appc-db-2 | 0/1 | CrashLoopBackOff | 6 | 21h |
| dev-appc-appc-dgbuilder-54f488d7f4-xhsf6 | 0/1 | Init:0/1 | 3 | 26h |
| dev-dcaegen2-dcae-bootstrap-779767c49c-g4572 | 0/1 | Init:0/2 | 0 | 22h |
| dev-dcaegen2-dcae-config-binding-service-66b8b9968-wl8nc | 0/4 | Init:0/2 | 15 | 22h |
| dev-dcaegen2-dcae-dashboard-6bd544c546-tvdvj | 0/2 | Init:0/2 | 5 | 22h |
| dev-dcaegen2-dcae-deployment-handler-764bd8dd8f-ks65g | 0/2 | Init:0/3 | 5 | 22h |
| dev-dcaegen2-dcae-policy-handler-7bb596f8c9-6rct8 | 0/2 | Init:0/3 | 5 | 22h |
| dev-dcaegen2-dcae-servicechange-handler-5b9ccdfb9d-bcvrq | 0/1 | CrashLoopBackOff | 26 | 21h |
| dev-dmaap-dmaap-bc-6b8c7494f9-xrzlq | 0/1 | Init:1/2 | 2 | 26h |
| dev-dmaap-dmaap-bc-post-install-vgp5x | 0/1 | Error | 0 | 21h |
| dev-dmaap-message-router-mirrormaker-656ddc54c6-ckcj7 | 0/1 | CrashLoopBackOff | 27 | 21h |
| dev-sdnc-sdnc-ueb-listener-55dd7886c6-dstcc | 0/1 | CrashLoopBackOff | 31 | 21h |
Attached you an find:
-The result of $ kubectl get pods -n onap
-The configuration file used
-The robot healthcheck results
