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: container init caused \\\\\\\"rootfs_linux.go:53: 
mounting 
\\\\\\\\\\\\\\\"/dockerdata-nfs/onap/aai/elasticsearch/config/elasticsearch.yml\\\\\\\\\\\\\\\"
 to rootfs 
\\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/d24d0f3bbefe3274713a8b518ef22382af64e379f5dfff823197792d7a226821\\\\\\\\\\\\\\\"
 at 
\\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/d24d0f3bbefe3274713a8b518ef22382af64e379f5dfff823197792d7a226821/usr/share/elasticsearch/config/elasticsearch.yml\\\\\\\\\\\\\\\"
 caused \\\\\\\\\\\\\\\"not a directory\\\\\\\\\\\\\\\"\\\\\\\"\\\"\\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: container init caused \\\\\\\"rootfs_linux.go:53: 
mounting 
\\\\\\\\\\\\\\\"/dockerdata-nfs/onap/log/filebeat/log4j/filebeat.yml\\\\\\\\\\\\\\\"
 to rootfs 
\\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/a9bbf536908afe8eab4aa9cfda6bd3bbb1e4b9d62ac1a1b2a50a7e4487f1b12a\\\\\\\\\\\\\\\"
 at 
\\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/a9bbf536908afe8eab4aa9cfda6bd3bbb1e4b9d62ac1a1b2a50a7e4487f1b12a/usr/share/filebeat/filebeat.yml\\\\\\\\\\\\\\\"
 caused \\\\\\\\\\\\\\\"not a directory\\\\\\\\\\\\\\\"\\\\\\\"\\\"\\n\""}  






Any idea?







Thanks,


Huabing
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to