In order to see if these are some new errors or just leftovers from previous crashes, I'd recommend deleting the contents of /dockerdata-nfs/dev-portal directory (its on NFS node) before redeploying dev-portal (using Helm).
Steps: 1. Undeploy dev-portal using Helm 2. Remove /dockerdata-nfs/dev-portal directory 3. Deploy dev-portal using Helm Piotr Darosz ________________________________ From: Balan, Prabhu, Vodafone Group (External) <[email protected]> Sent: Wednesday, August 7, 2019 3:09:42 PM To: Darosz, Piotr (Nokia - PL/Wroclaw) <[email protected]>; [email protected] <[email protected]> Subject: RE: [PORTAL]-Dublin - Struck in PodInitializating Many thanks Piotr. I have incremented the readiness (initialdelayseconds) and increased the resource quota and redeployed it. Again it is going back to CrashLoopBackOff, but this time error is different. Quick snapshot below. Any thoughts? [cid:[email protected]] Thanks, Prabhu. C2 General From: Darosz, Piotr (Nokia - PL/Wroclaw) <[email protected]> Sent: 07 August 2019 06:25 To: [email protected]; Balan, Prabhu, Vodafone Group (External) <[email protected]> Subject: Re: [PORTAL]-Dublin - Struck in PodInitializating Hi, it may be that due to lack of cpu/memory resources, a dev-portal-portal-db pod is taking so long to initialize that it just can't initialize fully before readiness probe kicks in and restart it (large restart count suggests it could be an issue). You can try editing the deployment dev-portal-portal-db and increment the readinessProbe.initialDelaySeconds setting. Another thing to consider would be to increase resource quota for database container in the same deployment (there is a key named "resources" for that). Piotr Darosz ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Balan, Prabhu, Vodafone Group (External) via Lists.Onap.Org <[email protected]<mailto:[email protected]>> Sent: Tuesday, August 6, 2019 10:49:58 AM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] [PORTAL]-Dublin - Struck in PodInitializating Hi, I have installed Dublin release 4.0.0, but some of the pods are struck in Init:Error stage. Below screenshot shows the pods for portal in PodInitializing stage. Can’t debug further. Any insights would be helpful. Docker version: 18.06.0-ce Kubernetes version: 1.15.1 Any help would be appreciated. [cid:[email protected]] Thanks, Prabhu. C2 General -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18464): https://lists.onap.org/g/onap-discuss/message/18464 Mute This Topic: https://lists.onap.org/mt/32774975/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
