Hi Michael,

I am also getting the same issue.

I am using git 'master' branch to deploy ONAP.


Attaching the docker log output for sparky-be and aai-resources containers.

Also, for me the deployment fails after timeout for aai-resources container. 
aai-traversal was not started at-all.


Thanks,

Arun

________________________________
From: onap-discuss-boun...@lists.onap.org <onap-discuss-boun...@lists.onap.org> 
on behalf of Michael O'Brien <frank.obr...@amdocs.com>
Sent: Tuesday, August 8, 2017 9:54:35 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] 1.1 deployment: AAI vm1 traversal and model-loader 
container failure on startup on JAXB dup field "invStatus" during v11 
initialization

Team,
   We are moving off of 1.0.0 – started bringing up 1.1.0/master on Friday.
   For 1.1/master - having an issue bringing up the last 3 containers on AAI-1 
(the resources:8447, traversal:8446 and the API model-loader:8443) during 
deploy_vm1.sh  at line 151 during the wait on aai-resources just after 
sparky-be started up.
  Both the 3rd and 2nd last containers (resources and traversal) fail with the 
same jaxb exception before we get to loading the last critical API model-loader 
container.

   Just wondering if anyone else had an issue with the 20170804 tagged master 
build – Note I am picking up 20170807 but should be the same as the 4th.
   Btw it would be very nice if we could start tagging builds – especially the 
ones that passed E2E integration tests – so we would not have to pick up master.

   8447 is timing out waiting for the container to start.
   If I start the 8446 container manually I get an EclipseLink exception on a 
duplicate field name during ATP (code generation) loading the bean – the same 
for both resources and traversal. (btw the Eclipselink guys are still in 
downtown Ottawa) – this may be a secondary exception in this case
   This field was introduced in OXM v9 and is still in v11 and looks ok to me 
(the actual class is only generated – so check the xml fle) – just in case 
anyone remembers a recent change in AAI’s schema that would break code 
generation on jetty startup.

   Raised the following to track it.
https://jira.onap.org/browse/AAI-140<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_AAI-2D140&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=W-_l-cx9LSBAVf5NqhdzbEM4rxBEINW0Q6QuiZ-E2GI&s=-LT3ZUUo6RyrjTtStRzW0OBEVjc9FPcoLt-FepWAwUg&e=>

Creating testconfig_sparky-be_1
Waiting for 'testconfig_aai-resources.api.simpledemo.openecomp.org_1' 
deployment to finish ...
...
Waiting for 'testconfig_aai-resources.api.simpledemo.openecomp.org_1' 
deployment to finish ...
ERROR: testconfig_aai-resources.api.simpledemo.openecomp.org_1 deployment 
failed.
2017-08-08 03:12:04,154 - util.py[WARNING]: Failed running 
/var/lib/cloud/instance/scripts/part-001 [1]
2017-08-08 03:12:04,155 - cc_scripts_user.py[WARNING]: Failed to run module 
scripts-user (scripts in /var/lib/cloud/instance/scripts)
2017-08-08 03:12:04,155 - util.py[WARNING]: Running scripts-user (<module 
'cloudinit.config.cc_scripts_user' from 
'/usr/lib/python2.7/dist-packages/cloudinit/config/cc_scripts_user.pyc'>) failed
Cloud-init v. 0.7.5 finished at Tue, 08 Aug 2017 03:12:04 +0000. Datasource 
DataSourceConfigDriveNet [net,ver=2][source=/dev/xvdd].  Up 912.76 seconds


root@vm1-aai-inst1:/opt/test-config# docker logs 
testconfig_aai-resources.api.simpledemo.openecomp.org_1

Making EdgeLabel: [startsWith]

Exception in thread "main" java.lang.ExceptionInInitializerError

at 
org.openecomp.aai.introspection.ModelInjestor.getInstance(ModelInjestor.java:69)

at org.openecomp.aai.introspection.MoxyLoader.process(MoxyLoader.java:118)

at org.openecomp.aai.introspection.MoxyLoader.<init>(MoxyLoader.java:69)

at 
org.openecomp.aai.introspection.LoaderFactory.createLoaderForVersion(LoaderFactory.java:36)

at 
org.openecomp.aai.dbgen.SchemaGenerator.loadSchemaIntoTitan(SchemaGenerator.java:118)

at 
org.openecomp.aai.dbgen.SchemaGenerator.loadSchemaIntoTitan(SchemaGenerator.java:68)

at org.openecomp.aai.dbgen.GenTester.main(GenTester.java:120)

Caused by: Exception [EclipseLink-50072] (Eclipse Persistence Services - 
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.JAXBException

Exception Description: Duplicate Property named [invStatus] found on class 
[inventory.aai.onap.org.v11.PInterface]

at 
org.eclipse.persistence.exceptions.JAXBException.duplicatePropertyName(JAXBException.java:971)

at org.eclipse.persistence.jaxb.compiler.TypeInfo.addProperty(TypeInfo.java:314)

at 
org.eclipse.persistence.jaxb.compiler.TypeInfo.setProperties(TypeInfo.java:340)

at 
org.eclipse.persistence.jaxb.compiler.AnnotationsProcessor.buildTypeInfo(AnnotationsProcessor.java:864)


root@vm1-aai-inst1:/opt/test-config# docker logs 
testconfig_aai-traversal.api.simpledemo.openecomp.org_1

Exception [EclipseLink-50072] (Eclipse Persistence Services - 
2.6.2.v20151217-774c696): 
org.eclipse.persistence.exceptions.JAXBException|Exception Description: 
Duplicate Property named [invStatus] found on class 
[inventory.aai.onap.org.v11.PInterface]

at 
org.eclipse.persistence.exceptions.JAXBException.duplicatePropertyName(JAXBException.java:971)

at org.eclipse.persistence.jaxb.compiler.TypeInfo.addProperty(TypeInfo.java:314)

at 
org.eclipse.persistence.jaxb.compiler.TypeInfo.setProperties(TypeInfo.java:340)

at 
org.eclipse.persistence.jaxb.compiler.AnnotationsProcessor.buildTypeInfo(AnnotationsProcessor.java:864)





    thank you
    /michael


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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=W-_l-cx9LSBAVf5NqhdzbEM4rxBEINW0Q6QuiZ-E2GI&s=kbrdbZIBOaDgxcGxFxNLM8lgDDmEMQzM6eFDqxzuEpo&e=>

Attachment: aai_deploy_vm1.sh.log
Description: aai_deploy_vm1.sh.log

_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to