Re: #OOM Casablanca Portal Deployment Failed #oom
Kubectl -n onap get pod | grep dev-portal
And for any failed pods we need a log.
It could be a timing problem with the mariadb configuration jobs but it depends on what is going on in the environment.
Are you using the public-cloud overrides to loosen up the liveness probe and readiness problem intervals ?
It is worth doing a helm delete dev-portal –purge, helm deploy dev-portal ... (https://wiki.onap.org/pages/viewpage.action?pageId=29787124)
This will remove and re-deploy the portal and since the other pods are deployed there should be less competition for network/cpu during the cassandra and mariadb configuration phases.
Of course without the kubectl information it could be something completely different.
Helm deploy could also be a false failure since its a set 10 minute timeout and slow environments can mark the helm deplooyment failed but the pods actually are up and running. A healthdcheck would be the more postive test that the containers are functioning correctly and a kubectl -n onap get pods to confirm the pods are all int he running state as a precursor to the health check.
From: onap-discuss@... <onap-discuss@...> On Behalf Of Sitharaman T R
Sent: Thursday, June 13, 2019 4:07 PM
Subject: [onap-discuss] #OOM Casablanca Portal Deployment Failed