Hi, not sure if related to the crashloopbackoff issue, but before redeploying onap is better to make sure that the /dockerdata-nfs is empty and there are no k8s resources from the previous deployment, e.g. pvc…
David On 13 Feb 2020, at 12:38, lefteris.alexakis via Lists.Onap.Org<http://Lists.Onap.Org> <[email protected]<mailto:[email protected]>> wrote: Thanks Dom, In the meantime i undeploy onap and tried to repeat the steps again. Now only dmaap failed to deploy. ~/oom/kubernetes$ helm list |grep -v DEPLOYED NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE dev-dmaap 1 Thu Feb 13 10:50:42 2020 FAILED dmaap-4.0.1 onap ~/oom/kubernetes$ Checking the pods i see that kafka pods are crash looping . Do you think safe to continue? $ kubectl get pods | grep dmaap dev-dmaap-dbc-pg-0 1/1 Running 0 21s dev-dmaap-dbc-pg-1 1/1 Running 0 39m dev-dmaap-dbc-pgpool-6446c895f5-8h7pc 1/1 Running 0 41m dev-dmaap-dbc-pgpool-6446c895f5-ms8h6 1/1 Running 0 41m dev-dmaap-dmaap-bc-7497997cd9-x5l89 1/1 Running 0 41m dev-dmaap-dmaap-bc-post-install-zlz6r 0/1 Completed 0 41m dev-dmaap-dmaap-dr-db-0 0/1 CrashLoopBackOff 12 41m dev-dmaap-dmaap-dr-node-0 0/2 Init:0/2 0 7m11s dev-dmaap-dmaap-dr-prov-54dd9f9dcd-c4lvq 0/2 Init:0/1 4 41m dev-dmaap-message-router-0 0/1 Init:0/1 3 41m dev-dmaap-message-router-kafka-0 1/1 Running 0 41m dev-dmaap-message-router-kafka-1 0/1 CrashLoopBackOff 12 41m dev-dmaap-message-router-kafka-2 0/1 CrashLoopBackOff 12 41m dev-dmaap-message-router-mirrormaker-6dd84744f4-5bvbn 0/1 Init:1/2 4 41m dev-dmaap-message-router-post-install-4ffgq 1/1 Running 0 2m14s dev-dmaap-message-router-post-install-ktcn9 1/1 Terminating 0 35m dev-dmaap-message-router-zookeeper-0 1/1 Running 0 7m13s dev-dmaap-message-router-zookeeper-1 1/1 Running 0 41m dev-dmaap-message-router-zookeeper-2 1/1 Running 0 41m dev-sdnc-sdnc-dmaap-listener-db7b4dc44-5t6g6 0/1 Init:0/1 0 20m Thanks Lefteris ________________________________ From: LUNANUOVA, DOMINIC (DOMINIC) <[email protected]<mailto:[email protected]>> Sent: Wednesday, February 12, 2020 3:46 PM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; Alexakis, Lefteris <[email protected]<mailto:[email protected]>> Subject: RE: [onap-discuss] ONAP Dublin installation The DMaaP team reviewed this and concur with Aniello. The helm failure is often due to the deployment timeout being reached before all jobs complete. See https://wiki.onap.org/display/DW/DMaaP+Deployment+Guide+-+Dublin on guidance to increase the timeout param But pods listed in the original post look OK (the DR DB pod crash can usually be safely ignored) -Dom From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aniello Paolo Malinconico Sent: Wednesday, February 12, 2020 8:23 AM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] ONAP Dublin installation Regarding the Helm error (FAILED), I had the same issue. But even if Helm command returns that error, the dmaap and so component were successfully deployed in my case. I think it's the same for you. You can check if the dmaap and so pods are getting up with the kubectl get pods --all-namespaces command. Thanks, Aniello Paolo Malinconico -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20008): https://lists.onap.org/g/onap-discuss/message/20008 Mute This Topic: https://lists.onap.org/mt/71209715/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
