Update: closed the issue as we come up ok on the secondary DFW DC with pure 1.0.0 artifacts (my mistake on this deployment mixing in 1.1.0) I was able to bring up the vFW VM's to just before traffic generation OK
using pure 1.0.0 we are OK, demo stack created on DFW obrienbiometrics:onap michaelobrien$ openstack stack list +--------------------------------------+------------+-----------------+---------------------+--------------+ | ID | Stack Name | Stack Status | Creation Time | Updated Time | +--------------------------------------+------------+-----------------+---------------------+--------------+ | 4e578010-0197-4879-8fae-2d065ff65cc9 | DemoModule | CREATE_COMPLETE | 2017-06-07T19:00:09 | None | | 94e00ab9-4a49-4e7c-a6bd-7cc5e6eaae11 | ONAP30 | CREATE_COMPLETE | 2017-06-06T18:45:53 | None | +--------------------------------------+------------+-----------------+---------------------+--------------+ Thank you /michael From: [email protected] [mailto:[email protected]] On Behalf Of Michael O'Brien Sent: Wednesday, June 7, 2017 12:03 To: Josef Reisinger <[email protected]> Cc: [email protected] Subject: Re: [onap-discuss] 20170606 Rackspace deployment has VID issue with stopped MariaDB container Josef, Thank you - exactly the population script I was looking for. Noticed that this particular tenant was run with 1.1.0 instead of 1.0.0 - exposing it to more commit traffic - rerunning the stack with 1.0.0 like my other DC in the env file - will update the jira. artifacts_version: 1.0.0-SNAPSHOT /michael From: Josef Reisinger [mailto:[email protected]] Sent: Wednesday, June 7, 2017 11:20 To: Michael O'Brien <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] 20170606 Rackspace deployment has VID issue with stopped MariaDB container Michael, for older versions, that looks like the script /docker-entrypoint-initdb.d/vid-pre-init.sql has not run. you may try $ docker exec -it vid-mariadb bash #> mysql -uroot -pLF+tp_1WqgSY </docker-entrypoint-initdb.d/vid-pre-init.sql maybe you need to restart vis-server after that. Mit freundlichen Grüßen / Kind regards Josef Reisinger From: "Michael O'Brien" <[email protected]<mailto:[email protected]>> To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: 07.06.2017 17:01 Subject: [onap-discuss] 20170606 Rackspace deployment has VID issue with stopped MariaDB container Sent by: [email protected]<mailto:[email protected]> ________________________________ VID team, Hi, did a clean rackspace install twice using the 1700 20170606 and 0700 EDT 20170607 codebase on our secondary tenant (trying to get the vFW demo past TG config - was an old nexus repo URL in the 1.0.0 ZIP template) Having issues getting a pre-populated VID DB container to restart - raised https://jira.onap.org/browse/UCA-22 The demo.sh init fails with a 500 on a missing SYD DC - but this is secondary. (thanks for the log viewing procedure - Andrew Fenner) - there is nothing wrong with the init/preload demo scripts as they worked fine previously root@vm1-robot:/opt# vi authorization # test:test root@vm1-robot:/opt# docker cp authorization openecompete_container:/etc/lighttpd/authorization root@vm1-robot:/opt# docker exec -it openecompete_container bash root@99521eebd8b7:/# cp -r /share/logs/demo/InitDemo/ /var/opt/OpenECOMP_ETE/html Arguments: [ ${cloud_owner}='Rackspace' | ${cloud_region_id}='SYD' | ${cloud_type}='SharedNode' | ${owner_defined_type}='OwnerType' | ${cloud_region_version}='v1' | ${cloud_zone}='CloudZone' | ${tenant_id}='1035199' | ${tenant_name}='1035199' ] Turns out that the MariaDB container on the VID VM failed to start - as a result the Tomcat container on VID failed startup. Any calls to VID return a 500 on a resulting "No route to host" getting the hibernate connection. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSourceMap' defined in class path resource java.net.NoRouteToHostException: No route to host (Host unreachable) Tried to fix it by starting the maria db container, waiting, restarting the tomcat container - but now it looks like schema re-population is required. root@vm1-vid:~# docker start vid-mariadb vid-mariadb root@vm1-vid:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f01603ad520f nexus3.onap.org:10001/openecomp/vid:1.0-STAGING-latest "/tmp/vid/localize.sh" 3 hours ago Up 3 hours 0.0.0.0:8080->8080/tcp vid-server c4a3fd8ccf7e mariadb:10 "docker-entrypoint..." 3 hours ago Up 4 seconds 3306/tcp vid-mariadb wait root@vm1-vid:~# docker stop vid-server vid-server root@vm1-vid:~# docker start vid-server vid-server root@vm1-vid:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f01603ad520f nexus3.onap.org:10001/openecomp/vid:1.0-STAGING-latest "/tmp/vid/localize.sh" 3 hours ago Up 14 seconds 0.0.0.0:8080->8080/tcp vid-server c4a3fd8ccf7e mariadb:10 "docker-entrypoint..." 3 hours ago Up About a minute 3306/tcp vid-mariadb root@vm1-vid:~# docker exec -it vid-server bash root@f01603ad520f:/usr/local/tomcat# cat logs/localhost.2017-06-07.log 07-Jun-2017 14:34:59.550 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.loadOnStartup Servlet [dispatcher] in web application [/vid] threw load() exception com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'vid_openecomp_epsdk.schema_info' doesn't exist at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 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_______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss 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
