Hi Srini, AAI introduced some configuration changes yesterday (Wednesday) which resulted in the crash loop you are seeing. The problem has already been fixed locally and will be pushed to gerrit today. Thank you from pointing out the problem.
The OOM team (the Integration team is in the same situation) would appreciate a heads up from the project teams if there is a change in docker containers or configuration. We're happy to adapt to changes as they are made but there would be fewer interruptions if we knew of the changes in advance. Thanks, Roger OOM Team From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Srinivasa Goda Sent: Wednesday, September 20, 2017 11:58 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] ONAP on Kubernetes with Rancher Hi, I'm trying to bring up the ONAP on Kubernetes with rancher. Initially, I could bring it up but after sometime, i keep seeing some of the containers entering in 'CrashLoopBackOff' state and one container, <namespace>-aai is in state init:0/1 for long time. I tried re-install everything from Ubuntu1604 VM to rancher and ONAP. I don't see any change. Any clues, pointers? Thanks, Regards, Srini [Beta Tester Badge 3] This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss