Hi, Morgan, Thanks a lot for your quick response. For MDONA use case, as long as the version are in sync, we are fine. No specific version is preferred.
Thanks. Xin Miao Solution Engineering Fujitsu Network Communication (W)972-479-2263 (M)469-268-5226 2811 Telecom Drive Richardson, TX 75081, USA From: [email protected] [mailto:[email protected]] Sent: Monday, April 27, 2020 11:41 AM To: Miao, Xin <[email protected]>; Yang, Bin <[email protected]> Cc: Fujii, Satoshi/藤井 理史 <[email protected]>; [email protected]; PLATANIA, MARCO <[email protected]> Subject: RE:[onap-discuss] [onap-sdc] FW: Certify error at L1 UNI OK the error looks explicit - it is not always the case.. :) I had a look at the daily master the version is Image: nexus3.onap.org:10001/onap/sdc-backend:1.6.4 and for me OOM Master is the reference https://gating-results.onap.eu/results/onap_daily_pod4_master-527559474-04-27-2020_06-04/infrastructure-healthcheck/k8s/versions.html I suspect a staging version has been used Do you need specifically the 1.6.5 or maybe another use case is needed it? I will have a look at SB00 tomorrow. @Marco I think the best is to align on 1.6.4, no? otherwise we need to re-init the DB to align on 1.6.5 /Morgan NB: Lukasz reported some issues with AAF on SB-00 ________________________________ De : [email protected]<mailto:[email protected]> [[email protected]] Envoyé : lundi 27 avril 2020 15:51 À : Yang, Bin; RICHOMME Morgan TGI/OLN Cc : [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Objet : [onap-discuss] [onap-sdc] FW: Certify error at L1 UNI Hi, Bin/Morgan, We ran into the following error at SB00 during the MDONS integration test. Please refer to the error message and description in the following email message from last week. Although, there are some analysis output at SB00 cluster: ------------------------------------------------------------------------------------------------------------------------------------------------------------- There is image version mismatch between the pods. (sdc backend init job) kubectl describe -n onap pod dev-sdc-be-config-backend-s5g49 sdc-be-job: Container ID: Image: nexus3.onap.org:10001/onap/sdc-backend-init:1.6.4 (sdc backend app pod) dev-sdc-be-587cf8bdf8-kddv5 sdc-be: Container ID: docker://65750deccacd85472f342a08b650631c06ae80dc96cbc3d447c2edfb02a24130 Image: nexus3.onap.org:10001/onap/sdc-backend:1.6.5-20200422T113901Z and schema files registered in Cassandra database: sdcreleasenum | conformancelevel | timestamp | checksum | filename ---------------+------------------+---------------------------------+----------------------------------+---------- 1.6.4 | 11.0 | 2020-04-20 19:58:46.735000+0000 | 38301cc10612567839bd98cbd4e5e39d | SDC.zip sdc-backend-init populated schema files into database as 1.6.4 but sdc-be app pod is looking for 1.6.5 schema. We think that’s why we are seeing “CSAR packaging failed. TOSCA schema files … not found” error at certify. My suggestion is to use 1.6.5 for all sdc pods. Do we need to align all sdc pods to the same version and redeploy sdc? Thanks a lot, Xin Miao Solution Engineering Fujitsu Network Communication (W)972-479-2263 (M)469-268-5226 2811 Telecom Drive Richardson, TX 75081, USA From: Miao, Xin Sent: Thursday, April 23, 2020 5:41 PM To: Fujii, Satoshi/藤井 理史 <[email protected]<mailto:[email protected]>> Subject: Certify error at L1 UNI Hi, Satoshi-san, I ran into the following error when I tried to define resource type L1 UNI at Windriver SB00 (master) instance: [cid:[email protected]] Is it because the TOSCA version in resource-uni.yml file is out of date? Thanks, Xin Miao Solution Engineering Fujitsu Network Communication (W)972-479-2263 (M)469-268-5226 2811 Telecom Drive Richardson, TX 75081, USA _________________________________________________________________________________________________________________________ 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. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20861): https://lists.onap.org/g/onap-discuss/message/20861 Mute This Topic: https://lists.onap.org/mt/73304137/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
