Hello Michael, We are using heat template for ONAP deployment. Could you please suggest any workaround for heat based environment to bring up AAI.
-- Regards, Subhash Kumar Singh *************************************************************************************** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** *************************************************************************************** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whoseaddress is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure,reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, pleasenotify the sender by phone or email immediately and delete it! *************************************************************************************** From: Michael O'Brien [mailto:[email protected]] Sent: Monday, December 11, 2017 7:31 PM To: Subhash Kumar Singh <[email protected]>; [email protected] Subject: RE: [AAI] AAI resource container failed to start Subhash, Hi, the AAI team (thank you for the quick response and patch), Alexis and I fixed this regression around midnight Friday �C in release-1.1.0 �C only in OOM �C as we point away from the master git pull in chef The issue was detected by the hourly OOM build around 11AM Friday �C I don’t currently have room to run a master build �C but this is still likely failing In master it may still be an issue �C you may want to bring it up with the AAI team. Workaround is to use OOM release-1.1.0 for now. https://lists.onap.org/pipermail/onap-discuss/2017-December/006859.html https://jira.onap.org/browse/AAI-548 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Subhash Kumar Singh Sent: Monday, December 11, 2017 05:25 To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] [AAI] AAI resource container failed to start Hello AAI team, Today I tried to stack the ONAP but I observed that AAI dockers are exiting with chef related exception. Following are the details: Logs (aai-resouce container): http://paste.openstack.org/show/628593/ AAI_VM_2 containers: a098a2dd5d1a elasticsearch:2.4.1 "/docker-entrypoin..." 4 hours ago Up 4 hours 0.0.0.0:9200->9200/tcp, 9300/tcp elasticsearch 50b6ff7c51dc aaionap/hbase:1.2.0 "/bin/sh -c \"/entr..." 4 hours ago Up 4 hours 0.0.0.0:2181->2181/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:8085->8085/tcp, 0.0.0.0:9090->9090/tcp, 0.0.0.0:16000->16000/tcp, 0.0.0.0:16010->16010/tcp, 9095/tcp, 0.0.0.0:16201->16201/tcp, 16301/tcp testconfig_aai.hbase.simpledemo.onap.org_1 AAI_VM_1 containers: fc499710f233 nexus3.onap.org:10001/onap/aai-resources "/bin/bash /opt/ap..." 17 minutes ago Exited (1) 11 seconds ago testconfig_aai-resources.api.simpledemo.onap.org_1 Please let us know how to fix this issue. There is similar discussion in onap-discuss[1] mailing list. [1] https://lists.onap.org/pipermail/onap-discuss/2017-December/006853.html -- Regards, Subhash Kumar Singh *************************************************************************************** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** *************************************************************************************** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whoseaddress is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure,reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, pleasenotify the sender by phone or email immediately and delete it! ***************************************************************************************
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
