If I remember correctly, lately there’s a certificate issue with data router. I think a new certificate should be issued. If you need message router for your tests then you’re good to go. Data router won’t impact you.
Marco From: Calamita Agostino <[email protected]> Date: Wednesday, February 27, 2019 at 7:04 AM To: "PLATANIA, MARCO (MARCO)" <[email protected]>, "[email protected]" <[email protected]> Subject: R: [onap-discuss] dmaap-dr-node in CrashLoopBackOff - ONAP Casablanca Hi all, about “dmaap-dr-node in CrashLoopBackOff”, today I undeployed all dmaap component and redeployed it, but nothing has changed. dev-dmaap-dbc-pg-0 1/1 Running 0 1h 10.42.173.158 onapkm5 <none> dev-dmaap-dbc-pg-1 1/1 Running 0 1h 10.42.188.140 onapkm2 <none> dev-dmaap-dbc-pgpool-7b748d5894-mr2m9 1/1 Running 0 1h 10.42.237.193 onapkm3 <none> dev-dmaap-dbc-pgpool-7b748d5894-n6dks 1/1 Running 0 1h 10.42.192.244 onapkm2 <none> dev-dmaap-dmaap-bus-controller-6757c4c86-b2tmf 1/1 Running 0 1h 10.42.72.241 onapkm6 <none> dev-dmaap-dmaap-dr-db-bb4c67cfd-tm7td 1/1 Running 0 1h 10.42.152.59 onapkm1 <none> dev-dmaap-dmaap-dr-node-66c8749959-wl7g6 0/1 CrashLoopBackOff 19 1h 10.42.124.75 onapkm0 <none> dev-dmaap-dmaap-dr-prov-5c766b8d69-zqmjj 1/1 Running 0 1h 10.42.151.243 onapkm5 <none> dev-dmaap-message-router-fb9f4bc7d-rrs22 1/1 Running 0 1h 10.42.203.15 onapkm0 <none> dev-dmaap-message-router-kafka-5fbc897f48-4bpb6 1/1 Running 0 1h 10.42.78.141 onapkm4 <none> dev-dmaap-message-router-zookeeper-557954854-8d6p9 1/1 Running 0 1h 10.42.169.205 onapkm1 <none> But, in dmaap-bus-controller Pod, I see this error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979) at sun.security.ssl.Handshaker.process_record(Handshaker.java:914) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153) at org.onap.dmaap.dbcapi.client.DrProvConnection.doPostFeed(DrProvConnection.java:164) at org.onap.dmaap.dbcapi.service.FeedService.addFeed(FeedService.java:236) at org.onap.dmaap.dbcapi.resources.FeedResource.addFeed(FeedResource.java:121) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:143) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:160) at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:158) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:97) at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102) at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:303) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:286) at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1072) at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:399) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:835) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:224) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) at org.eclipse.jetty.server.Server.handle(Server.java:517) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) at java.lang.Thread.run(Thread.java:745) Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:352) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:260) at sun.security.validator.Validator.validate(Validator.java:260) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491) ... 58 more Caused by: java.security.cert.CertPathValidatorException: timestamp check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140) at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292) at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347) ... 64 more Caused by: java.security.cert.CertificateExpiredException: NotAfter: Sun Feb 17 16:21:17 GMT 2019 at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274) at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629) at sun.security.provider.certpath.BasicChecker.verifyTimestamp(BasicChecker.java:190) at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:144) at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125) ... 69 more < HTTP/1.1 500 Internal Server Error < Date: Wed, 27 Feb 2019 10:22:38 GMT < Content-Type: application/json < Content-Length: 80 * Server Jetty(9.3.z-SNAPSHOT) is not blacklisted < Server: Jetty(9.3.z-SNAPSHOT) < { [data not shown] 100 395 100 80 100 315 136 537 --:--:-- --:--:-- --:--:-- 536 * Connection #0 to host dmaap-bc left intact response={"code":500,"fields":"response","message":"Unexpected response from DR backend"}500 Thanks. Da: PLATANIA, MARCO (MARCO) [mailto:[email protected]] Inviato: martedì 26 febbraio 2019 17:32 A: Calamita Agostino <[email protected]>; [email protected] Oggetto: Re: [onap-discuss] dmaap-dr-node in CrashLoopBackOff - ONAP Casablanca UEB cluster not available is related to DMaaP/Message Router. SDNC UEB listener is down for the same reason as SDC. Some issue with DMaaP is affecting SDC and SDNC (but I guess some other container could be affected as well). Marco From: Calamita Agostino <[email protected]<mailto:[email protected]>> Date: Tuesday, February 26, 2019 at 11:08 AM To: "PLATANIA, MARCO (MARCO)" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: R: [onap-discuss] dmaap-dr-node in CrashLoopBackOff - ONAP Casablanca Hi Marco, this I tried http://{{sdc_ip}}:{{sdc_port}}/sdc1/rest/healthCheck<https://urldefense.proofpoint.com/v2/url?u=http-3A__-257b-257bsdc-5Fip-257d-257d-3A-257b-257bsdc-5Fport-257d-257d_sdc1_rest_healthCheck&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=FXpb-5FIwxyQPY9k8O26fzIcdDO-OAg3DjI9h3N6mao&s=RBWDh4SrzkoCRPq27-NvsjmuGKd2EFfK7eLOostaBYI&e=> and the answer is { "sdcVersion": "1.3.6", "siteMode": "unknown", "componentsInfo": [ { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK" }, { "healthCheckComponent": "TITAN", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "ES", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK" }, { "healthCheckComponent": "DE", "healthCheckStatus": "DOWN", "description": "U-EB cluster is not available" }, { "healthCheckComponent": "CASSANDRA", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "ON_BOARDING", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK", "componentsInfo": [ { "healthCheckComponent": "ZU", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK" }, { "healthCheckComponent": "CAS", "healthCheckStatus": "UP", "version": "2.1.17", "description": "OK" }, { "healthCheckComponent": "FE", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK" } ] }, { "healthCheckComponent": "DCAE", "healthCheckStatus": "UP", "version": "1.3.0", "description": "OK", "componentsInfo": [ { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.3.0", "description": "OK" }, { "healthCheckComponent": "TOSCA_LAB", "healthCheckStatus": "UP", "version": "1.3.0", "description": "OK" }, { "healthCheckComponent": "FE", "healthCheckStatus": "UP", "description": "OK" } ] }, { "healthCheckComponent": "FE", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK" } ] } U-EB cluster is not available. Is it related to sdnc-ueb-listener ? Thanks. Da: PLATANIA, MARCO (MARCO) [mailto:[email protected]] Inviato: martedì 26 febbraio 2019 16:44 A: [email protected]<mailto:[email protected]>; Calamita Agostino <[email protected]<mailto:[email protected]>> Oggetto: Re: [onap-discuss] dmaap-dr-node in CrashLoopBackOff - ONAP Casablanca Data router is not used for model distribution. Try to run healthcheck and see if SDC can talk to UEB (message router). If robot reports NONE, then there’s some issue. Otherwise look at the zookeeper/kafka/message router container status. It may be that zookeeper restarted and created some mess. If so you need to bounce zookeeper, kafka and message router container in this order, with a 30/40-second delay between one bounce operation and the other. Marco From: <[email protected]<mailto:[email protected]>> on behalf of Calamita Agostino <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday, February 26, 2019 at 10:22 AM To: "'[email protected]'" <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] dmaap-dr-node in CrashLoopBackOff - ONAP Casablanca Hi all, I’m using a ONAP Casablanca release 3.0.0 in order to test the Onboarding Service task on SDC. After Service Creation,Test and Approve steps, when I try to distribute the service ( that is login as op0001 and click on “Distribute” button ) I got this error: Internal Server Error Error: POL5000 In jira I found that this error is related to “dmaap-dr-node” pod that does not work correctly. Error-code POL5000 Internal Server Error. https://jira.onap.org/browse/SDC-1090<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDC-2D1090&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=3058W7WVEOTVttlFWZq4xJuTFvjraCcPHhou6bcF02M&s=mt2TyRZeXOSQmpRvwDwD_1N3CWXemdPGik0g91bRRaI&e=> In my Casablanca installation, this pod is in CrashLoopBackOff state . dev-dmaap-dr-node-66c8749959-sp6mf 0/1 CrashLoopBackOff 17 I saw that there was an issue related to expired certificate on AAF for dmaap-dr-node, and it is solved yestarday, but the Fix Version is Dublin “dev-dmaap-dmaap-dr-node pod does not come up due to https call to dev-dmaap-dmaap-dr-prov pod”: https://lists.onap.org/g/onap-discuss/topic/29919443#15653<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_g_onap-2Ddiscuss_topic_29919443-2315653&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=3058W7WVEOTVttlFWZq4xJuTFvjraCcPHhou6bcF02M&s=ne3lCzSWTC8YDN4zdshZUZbq1PXCb_jEyDVdvnzDYDU&e=> “[DR] AAF certs expired on dmaap-dr-prov and dmaap-dr-node”: https://jira.onap.org/browse/DMAAP-1048<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_DMAAP-2D1048&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=3058W7WVEOTVttlFWZq4xJuTFvjraCcPHhou6bcF02M&s=Tz9NH8jczE6RLStwDYjd9AsX3lR8jEMijKZhINCvflE&e=> Is there any way to apply this solution on Casablanca 3.0.0 or some workaround ? Thanks. Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.italtel.com_it_about_privacy_&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=3058W7WVEOTVttlFWZq4xJuTFvjraCcPHhou6bcF02M&s=i-YtPgHDLX1aowts0IYHugxQ_sogrP7kFikkdz9hpV4&e=> ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.italtel.com_it_about_privacy_&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=3058W7WVEOTVttlFWZq4xJuTFvjraCcPHhou6bcF02M&s=i-YtPgHDLX1aowts0IYHugxQ_sogrP7kFikkdz9hpV4&e=> Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.italtel.com_it_about_privacy_&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=FXpb-5FIwxyQPY9k8O26fzIcdDO-OAg3DjI9h3N6mao&s=K19scy3p23-jm-4zEg70YVq4knSpcFzIiHwiUKe_tZ8&e=> ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.italtel.com_it_about_privacy_&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=FXpb-5FIwxyQPY9k8O26fzIcdDO-OAg3DjI9h3N6mao&s=K19scy3p23-jm-4zEg70YVq4knSpcFzIiHwiUKe_tZ8&e=> Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.italtel.com_it_about_privacy_&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=VMsXGOcIl6vXEAvCO6T0Lc05NfcpOB83joM2-CErSMw&s=u-SrxTp_OzzF8qVV5B7pyqWE5ZFNu5pPWTryZKNoNTk&e=> ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.italtel.com_it_about_privacy_&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=VMsXGOcIl6vXEAvCO6T0Lc05NfcpOB83joM2-CErSMw&s=u-SrxTp_OzzF8qVV5B7pyqWE5ZFNu5pPWTryZKNoNTk&e=> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15768): https://lists.onap.org/g/onap-discuss/message/15768 Mute This Topic: https://lists.onap.org/mt/30152131/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
