Sylvain, Good question and thank you for syncing your deployment state with the rest of us. Some of the openecomp to onap namespace refactor is still going on – one went it 2 days ago to another component – it was fully OK. There is a small chance that runtime classloading – during spring container instantiation in a .forName() – the xml references to the class name were not updated – but these are very rare (Note: these are not caught by Jenkins jobs unless they deploy component or all of onap = CD)
I’ll take a look through the commits on master. I expect that a lot of these are version changes – like you found - that have not been done in the templates yet. We will also start a review of the docker version numbers to see if they match changes in prep of branching/releasing. When we get an official CD deployment job going on Jenkins – these should be caught and become historically traceable . I’ll see if we have these same issues on the Kubernetes deployment of ONAP – in its hourly CD Jenkins job. As of 1 hour ago We fail DCAE because the Jenkins CD job still needs proper config setup – so unrelated – my bad! We fail sdc, appc and policy – where only appc failure lines up with yourself We pass on sdngc, portal and SO – where you fail I will also do a pass to verify that the deployment yamls are up to date with the latest versions http://jenkins.onap.info/job/oom-cd/ 16:32:09 Basic DCAE Health Check [ WARN ] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0e52d16550>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /healthcheck 16:32:10 Basic SDNGC Health Check | PASS | 16:32:10 ------------------------------------------------------------------------------ 16:32:10 Basic A&AI Health Check | PASS | 16:32:10 ------------------------------------------------------------------------------ 16:32:12 Basic Policy Health Check | FAIL | 16:32:12 'False' should be true. 16:32:12 ------------------------------------------------------------------------------ 16:32:25 Basic MSO Health Check | PASS | 16:32:25 ------------------------------------------------------------------------------ 16:32:25 Basic ASDC Health Check | FAIL | 16:32:25 500 != 200 16:32:25 ------------------------------------------------------------------------------ 16:32:25 Basic APPC Health Check | FAIL | 16:32:25 404 != 200 16:32:25 ------------------------------------------------------------------------------ 16:32:25 Basic Portal Health Check | PASS | 16:32:25 ------------------------------------------------------------------------------ 16:32:25 Basic Message Router Health Check | PASS | 16:32:25 ------------------------------------------------------------------------------ 16:32:26 Basic VID Health Check | PASS | Looking at SDNGC for example – over the past 3 days, the hourly build logged a healthcheck failure on SDNC - Failing until 0700 EDT yesterday, and once at 2200 last night (but that one looks like a performance spike – as the build took 30 min to deploy instead of the usual 15 min – because we are temporarily using a host with half the cores) - So SDNGC has been passing since 7am EDT yesterday for us – using master http://kibana.onap.info:5601/app/kibana#/discover?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-7d,mode:quick,to:now))&_a=(columns:!(_source),index:AV-vxHzpUcDKD8zJ1zbn,interval:auto,query:(query_string:(query:'message:%20%20(%22SDNGC%22%20AND%20%22FAIL%22)')),sort:!('@timestamp',desc)) SO has always passed for the last 3 days http://kibana.onap.info:5601/app/kibana#/discover?_g=(refreshInterval:('$$hashKey':'object:1605',display:'5%20seconds',pause:!f,section:1,value:5000),time:(from:now-7d,mode:quick,to:now))&_a=(columns:!(_source),index:AV-vxHzpUcDKD8zJ1zbn,interval:auto,query:(query_string:(query:'message:%20%20(%22MSO%22%20AND%20%22PASS%22)')),sort:!('@timestamp',desc)) thank you /michael From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, November 15, 2017 11:26 To: [email protected] Subject: [onap-discuss] [HEAT Deployment] Many failures on components Hello guys, I’ve started a Heat deployment 4h ago with fresh pull just before. At the end of the deployment, I’ve got 6 over 30 tests only which are green : * DCAE fails (but this is because of multi cloud) * SDNGC fails * APPC fails * Portal fails * SO fails for SDNC, it appears that the init script pull 1.1.0-release branch which is quite outdated compared to master. When launching with docker-compose from master, it starts and healthcheck is OK for APPC, I see some errors in the logs: Error: Could not find or load main class org.openecomp.sdnc.dg.loader.DGXMLGenerator Error: Could not find or load main class org.openecomp.sdnc.dg.loader.DGXMLLoad Error: Could not find or load main class org.openecomp.sdnc.dg.loader.DGXMLActivate After changing to 1.2 instead of 1.1 for the docker version, healthcheck pass. For portal, I’ve got a timeout from db access, after after a relaunch of the portal it works For SO, a restart of the script did the trick (forgot to see the error first sorry) For multicloud, I have pulling error from nexus : Pulling repository nexus3.onap.org:10001/onap/msb/msb_discovery Error: image onap/msb/msb_discovery:v1.0.0 not found Pulling repository nexus3.onap.org:10001/onap/msb/msb_apigateway nexus3.onap.org Error: image onap/msb/msb_apigateway:v1.0.0 not found Am I the only one having all these errors? How can I debug multicloud? Thanks! -- [cid:[email protected]]<http://www.orange.com/> Sylvain Desbureaux Ingénieur concepteur développeur ORANGE/IMT/OLN/CNC/NCA/SINA Fixe : +33 2 96 07 13 80 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2096%2007%2013%2080> Mobile : +33 6 71 17 25 57 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2071%2017%2025%2057> [email protected]<mailto:[email protected]> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. 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
