Huabing, Also forgot to mention – make sure to source setenv.bash – for even if you don’t need HELM_APPS because you are –a ing a single component – you still need the other env variables to be able to pull your docker images – this would also cause crashloopbackoffs – (bad name – it really means the pod is waiting for an image or a container dependency) Hope that helps
Try the cd.sh script in progress for the F2F at https://github.com/obrienlabs/onap-root/blob/master/cd.sh /michael From: [email protected] [mailto:[email protected]] On Behalf Of Michael O'Brien Sent: Sunday, December 3, 2017 01:22 To: [email protected]; [email protected] Subject: Re: [onap-discuss] Get errors when deploying AAI via OOM Huabing, Hi, those file/directory errors are red-herrings – they occur during docker image loading – if you continue to have them then likely your config pod did not run correctly A common error is not having your onap-parameters.yaml configured properly – check the values against your rc file. When you run the config pod – verify it is not in error – tail the log and check for a missing env variable Also if you are switching from master to release-1.1.0 - make sure to delete your config pod and rm –rf the entire /dockerdata-nfs See the onap on kubernetes page – there is a manual quickstart and an almost-automated set of 3 scripts to bring up a bare system. If you run the cd.sh script – the same one I run on the Amsterdam.onap.info CD server – it will automate the entire teardown/recreate of a fresh pull from OOM and deployment – running healthcheck at the end for you. Get the latest prepull docker scripts for master or 1.1.0 as well from the page https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation thank you /michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Thursday, November 30, 2017 04:28 To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] Get errors when deploying AAI via OOM Hi, I got the below errors when deploying AAI via OOM. ./createAll.bash -a aai -n onap kubectl get pods -n onap-aai elasticsearch-622738319-71vjg 0/1 rpc error: code = 2 desc = failed to start container "698a9bc2989c227a34b91018fe0f840b2f293bcb9daceb50ec36c7550308374e": Error response from daemon: {"message":"invalid header field value \"oci runtime error: container_linux.go:247: starting container process caused \\\"process_linux.go:359<file:///\\%22process_linux.go:359>: container init caused \\\\\\\"rootfs_linux.go:53<file:///\\%22rootfs_linux.go:53>: mounting \\\\\\\\\\\\\\\"/dockerdata-nfs/onap/aai/elasticsearch/config/elasticsearch.yml\\\\\\\\\\\\\\\<file:///\\%22\dockerdata-nfs\onap\aai\elasticsearch\config\elasticsearch.yml\>" to rootfs \\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/d24d0f3bbefe3274713a8b518ef22382af64e379f5dfff823197792d7a226821\\\\\\\\\\\\\\\<file:///\\%22\var\lib\docker\aufs\mnt\d24d0f3bbefe3274713a8b518ef22382af64e379f5dfff823197792d7a226821\>" at \\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/d24d0f3bbefe3274713a8b518ef22382af64e379f5dfff823197792d7a226821/usr/share/elasticsearch/config/elasticsearch.yml\\\\\\\\\\\\\\\<file:///\\%22\var\lib\docker\aufs\mnt\d24d0f3bbefe3274713a8b518ef22382af64e379f5dfff823197792d7a226821\usr\share\elasticsearch\config\elasticsearch.yml\>" caused \\\\\\\\\\\\\\\"not<file:///\\%22not> a directory\\\\\\\\\\\\\\\"\\\\\\\"\\\"\\n\<file:///\\n\>""} sparky-be-1292339831-ncldx 0/2 rpc error: code = 2 desc = failed to start container "c6574fe2e3fd7544234e97b24aadd46a613be2be348c4273edd68962102cfa2c": Error response from daemon: {"message":"invalid header field value \"oci runtime error: container_linux.go:247: starting container process caused \\\"process_linux.go:359<file:///\\%22process_linux.go:359>: container init caused \\\\\\\"rootfs_linux.go:53<file:///\\%22rootfs_linux.go:53>: mounting \\\\\\\\\\\\\\\"/dockerdata-nfs/onap/log/filebeat/log4j/filebeat.yml\\\\\\\\\\\\\\\<file:///\\%22\dockerdata-nfs\onap\log\filebeat\log4j\filebeat.yml\>" to rootfs \\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/a9bbf536908afe8eab4aa9cfda6bd3bbb1e4b9d62ac1a1b2a50a7e4487f1b12a\\\\\\\\\\\\\\\<file:///\\%22\var\lib\docker\aufs\mnt\a9bbf536908afe8eab4aa9cfda6bd3bbb1e4b9d62ac1a1b2a50a7e4487f1b12a\>" at \\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/a9bbf536908afe8eab4aa9cfda6bd3bbb1e4b9d62ac1a1b2a50a7e4487f1b12a/usr/share/filebeat/filebeat.yml\\\\\\\\\\\\\\\<file:///\\%22\var\lib\docker\aufs\mnt\a9bbf536908afe8eab4aa9cfda6bd3bbb1e4b9d62ac1a1b2a50a7e4487f1b12a\usr\share\filebeat\filebeat.yml\>" caused \\\\\\\\\\\\\\\"not<file:///\\%22not> a directory\\\\\\\\\\\\\\\"\\\\\\\"\\\"\\n\<file:///\\n\>""} Any idea? Thanks, Huabing 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 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 [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
