Thank you so much Morgan for the updates. Let's decide what the path forward during today's PTL call.
Best regards Catherine From: morgan.richo...@orange.com <morgan.richo...@orange.com> Sent: Thursday, August 6, 2020 4:38 PM To: TIMONEY, DAN <dt5...@att.com>; DESBUREAUX Sylvain TGI/OLN <sylvain.desbure...@orange.com>; Nowak, Damian (Nokia - PL/Wroclaw) <damian.no...@nokia.com>; onap-tsc@lists.onap.org; Lefevre, Catherine <catherine.lefe...@intl.att.com>; dmcbr...@linuxfoundation.org Cc: Closset, Christophe <christophe.clos...@intl.att.com>; Sonsino, Ofir <ofir.sons...@intl.att.com>; seshu.kuma...@huawei.com; onap-rele...@lists.onap.org; DEBEAU Eric TGI/OLN <eric.deb...@orange.com>; HARDY Thierry TGI/OLN <thierry.ha...@orange.com>; BONKUR, VENKAT <vb8...@att.com>; FREEMAN, BRIAN D <bf1...@att.com>; RAJEWSKI Lukasz O-PL <lukasz.rajew...@orange.com>; SMOKOWSKI, STEVEN <ss8...@att.com>; KULESHOV, ELENA <ek1...@att.com>; SHAH, SANDEEP <ss0...@att.com>; TATTAVARADA, SUNDER <sta...@research.att.com>; Krzysztof Opasiak <k.opas...@samsung.com> Subject: RE:[onap-tsc] [Onap-release] [Maintenance Release]Status Update Hi El Alto regarding the 2 items - 1309: this test deals with the onboarding/distribution/instantiation of a simple Ubuntu VM through ONAP in the logs, we can see that the SDC onboarding part seems OK, distribution is initiated, SO and AAI got the distribution but not the SDNC If we look at more recent occurrences - today & yesterday: https://gating-results.onap.eu/results/onap_daily_pod4_elalto-673384920/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D673384920_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=r1cZkhlv345C3s5uLDXbOpS2GY7W9ayZcGnAZ0Aaho8&s=EhOKwgXFp2qFsumoZxxobUP8IvP_T7B9TWvUaR726qs&e=> sdnc distribution is completed test is OK up to the instantiation final step => SO message Exception during create VF 404 NOT FOUND: So the distribution error seems to be transitient I updated the JIRA the error seen since monday seems reproducible and has been reported to SO. @Seshu, did you find anything in this area? -1308, onboarding /distribution were OK, we got another error at the last instantiation step "No preload data found to match vnf-name" But we did not get the issue in August so far..It could be a timing issue. Note for El alto I also remarked that the reporting page was buggy postinstall and healthdist are OK however they are reported as Failed https://gating-results.onap.eu/results/onap_daily_pod4_elalto-673384920/healthcheck/postinstall/postinstall/report.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D673384920_healthcheck_postinstall_postinstall_report.html&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=r1cZkhlv345C3s5uLDXbOpS2GY7W9ayZcGnAZ0Aaho8&s=ZPq7WjMh9oXCN6PVLmZMBG466WoX--2FMbz-nA1W0Aw&e=> https://gating-results.onap.eu/results/onap_daily_pod4_elalto-673384920/healthcheck/healthdist/healthdist/report.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D673384920_healthcheck_healthdist_healthdist_report.html&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=r1cZkhlv345C3s5uLDXbOpS2GY7W9ayZcGnAZ0Aaho8&s=Zq8m9TofdWNaiifr2bxDAV-RlHrWRuxxCq5kJ1KaV4w&e=> and regarding the healthchecks the score is 58 PASS / 3 FAIL - APPC (but we can see in onap-k8s that the config map was not created) - modeling (which was used to have also some timing issue - OOF-CMSO so for the El Alto, the main concern is the error at the end of the instantiation, I think we can live with the other issues. @Seshu, I send you a dedicated mail, I think I found a nice exception in the adapter Frankfurt Last runs were OK, Sylvain already mentioned his green light I agree, last CI runs are OK for me I have just an open question for Vijay on DCAE. It seems that there is 1 patch in dcae (master properly backported to fra,kfurt), but no dockers have been produced including this change, so I think it is not onboarded yet. (see my comments in the JIRA https://jira.onap.org/browse/DCAEGEN2-2249<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_DCAEGEN2-2D2249&d=DwQF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=r1cZkhlv345C3s5uLDXbOpS2GY7W9ayZcGnAZ0Aaho8&s=cjygo2Iefpjyt8ua6hcZ4S2coqdzugBR8_pXlT9U4hU&e=>) Otherwise the list (of the projects impactes by the maintenance release) of David and my list almost corresponds - SDC - POLICY - CCSDK - SO - CLAMP - AAF - OOM - TESTSUITE* - SDNC* - DCAE? *: difference between the 2 lists - TESTUITE = minor changes in cds robot tests => release note updated - SDNC no JIRA found, but new version detected (1.8.4 versus 1.8.3 in the release) you can visualize the difference between Frankfurt and its first maintenance release base on the daily runs extracted from onap-k8s test case) https://docs.google.com/spreadsheets/d/1t3GNRtabdkVxG4ZAxqBJ-X7OO-Zv6xRwd8KrR52V9zU/edit#gid=1893816488<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spreadsheets_d_1t3GNRtabdkVxG4ZAxqBJ-2DX7OO-2DZv6xRwd8KrR52V9zU_edit-23gid-3D1893816488&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=r1cZkhlv345C3s5uLDXbOpS2GY7W9ayZcGnAZ0Aaho8&s=nBkDOWxEbl5NoBQYGjXq_7_lNhRh7hyoRLQNIYzwr_0&e=> Finally, we got an issue with clamp (maria not starting asking for a pwd) but ONLY in windriver environement. This test on the daily Frankfurt is OK in Orange, DT and Nokia labs so Investigation is in progress on windriver side. /Morgan ________________________________ De : TIMONEY, DAN [dt5...@att.com] Envoyé : jeudi 30 juillet 2020 16:35 À : DESBUREAUX Sylvain TGI/OLN; Nowak, Damian (Nokia - PL/Wroclaw); onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; LEFEVRE, CATHERINE; dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org> Cc : CLOSSET, CHRISTOPHE; SONSINO, OFIR; seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>; onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>; DEBEAU Eric TGI/OLN; RICHOMME Morgan TGI/OLN; HARDY Thierry TGI/OLN; BONKUR, VENKAT; FREEMAN, BRIAN D; RAJEWSKI Lukasz O-PL; SMOKOWSKI, STEVEN; KULESHOV, ELENA; SHAH, SANDEEP; TATTAVARADA, SUNDER; Nowak, Damian (Nokia - PL/Wroclaw); Krzysztof Opasiak Objet : Re: [onap-tsc] [Onap-release] [Maintenance Release]Status Update Sylvain, all: I wanted to provide an update on the 2 SDNC issues noted below: - July 23th: Issue between SDC and SDNC (we don't see SDNC "ack" the reception of distribution) (https://gating-results.onap.eu/results/onap_daily_pod4_elalto-652346521/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D652346521_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log&d=DwQF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw&s=qsa4LJzl93jRDHAZip-h8GC8aa2g7Es3nx-5XtSzxiE&e=>). I tried to restart but always the same issue Jira SDNC-1309 (https://jira.onap.org/browse/SDNC-1309<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDNC-2D1309&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=r1cZkhlv345C3s5uLDXbOpS2GY7W9ayZcGnAZ0Aaho8&s=vfakJ_VXkmTonNDkJsKKKwC62Oj4a7EJ02ICzZ9quuE&e=>) opened for this. I didn't see any reference in the debug.log here to a distribution to SDNC, but I did see distributions to CDS. Is that what you're referring to? Or are you saying there should have been a distribution that isn't listed? - July 24th: Issue on SDNC (preload data doesn't seems to be here but we have a 200 OK when uploading) (https://gating-results.onap.eu/results/onap_daily_pod4_elalto-654306232/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D654306232_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw&s=N5pCbrdUj3HPaq7a8yr2tBwFRWmBrCjPD3Pu1icMZaw&e=>). I tried to restart but always the same issue Jira SDNC-1308 (https://jira.onap.org/browse/SDNC-1308<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDNC-2D1308&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=r1cZkhlv345C3s5uLDXbOpS2GY7W9ayZcGnAZ0Aaho8&s=aHl5cQt7nhYHYeOErJsp0rgznPM99jGV4hM76fskwJE&e=>) opened for this. This is most likely a timing issue. In the OpenDaylight platform, data writes occur after the response is returned - so if a GET is done right after a POST, it sometimes is not yet found. This can be corrected via a design change, but it is a significant amount of work and this particular API has been deprecated. I believe this is already addressed in GENERIC-RESOURCE-API - which replaces VNF-API. So I would prefer to document this as a known issue in El Alto and leave it unresolved. Thanks! Dan From: "TIMONEY, DAN" <dt5...@att.com<mailto:dt5...@att.com>> Date: Monday, July 27, 2020 at 10:14 AM To: "sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>" <sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>>, "Nowak, Damian (Nokia - PL/Wroclaw)" <damian.no...@nokia.com<mailto:damian.no...@nokia.com>>, "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>, "LEFEVRE, CATHERINE" <catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>>, "dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>" <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>> Cc: "CLOSSET, CHRISTOPHE" <christophe.clos...@intl.att.com<mailto:christophe.clos...@intl.att.com>>, "SONSINO, OFIR" <ofir.sons...@intl.att.com<mailto:ofir.sons...@intl.att.com>>, "seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>" <seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>, "onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>" <onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>, DEBEAU Eric TGI/OLN <eric.deb...@orange.com<mailto:eric.deb...@orange.com>>, RICHOMME Morgan TGI/OLN <morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>>, HARDY Thierry TGI/OLN <thierry.ha...@orange.com<mailto:thierry.ha...@orange.com>>, "BONKUR, VENKAT" <vb8...@att.com<mailto:vb8...@att.com>>, "FREEMAN, BRIAN D" <bf1...@att.com<mailto:bf1...@att.com>>, RAJEWSKI Lukasz O-PL <lukasz.rajew...@orange.com<mailto:lukasz.rajew...@orange.com>>, "SMOKOWSKI, STEVEN" <ss8...@att.com<mailto:ss8...@att.com>>, ELENA KULESHOV <ek1...@att.com<mailto:ek1...@att.com>>, "SHAH, SANDEEP" <ss0...@att.com<mailto:ss0...@att.com>>, "TATTAVARADA, SUNDER" <sta...@research.att.com<mailto:sta...@research.att.com>>, "Nowak, Damian (Nokia - PL/Wroclaw)" <damian.no...@nokia.com<mailto:damian.no...@nokia.com>>, Krzysztof Opasiak <k.opas...@samsung.com<mailto:k.opas...@samsung.com>> Subject: Re: [onap-tsc] [Onap-release] [Maintenance Release]Status Update Sylvain, I don't see Jiras associated with the 2 SDNC issues below. I'll create Jiras, although I would appreciate in the future if the person reporting the issue does so in Jira so it does not get missed in the deluge of emails we all get. Thanks! Dan From: "sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>" <sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>> Date: Friday, July 24, 2020 at 3:26 AM To: "Nowak, Damian (Nokia - PL/Wroclaw)" <damian.no...@nokia.com<mailto:damian.no...@nokia.com>>, "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>, "LEFEVRE, CATHERINE" <catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>>, "dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>" <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>> Cc: "CLOSSET, CHRISTOPHE" <christophe.clos...@intl.att.com<mailto:christophe.clos...@intl.att.com>>, "SONSINO, OFIR" <ofir.sons...@intl.att.com<mailto:ofir.sons...@intl.att.com>>, "TIMONEY, DAN" <dt5...@att.com<mailto:dt5...@att.com>>, "seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>" <seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>, "onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>" <onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>, DEBEAU Eric TGI/OLN <eric.deb...@orange.com<mailto:eric.deb...@orange.com>>, RICHOMME Morgan TGI/OLN <morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>>, HARDY Thierry TGI/OLN <thierry.ha...@orange.com<mailto:thierry.ha...@orange.com>>, "BONKUR, VENKAT" <vb8...@att.com<mailto:vb8...@att.com>>, "FREEMAN, BRIAN D" <bf1...@att.com<mailto:bf1...@att.com>>, RAJEWSKI Lukasz O-PL <lukasz.rajew...@orange.com<mailto:lukasz.rajew...@orange.com>>, "SMOKOWSKI, STEVEN" <ss8...@att.com<mailto:ss8...@att.com>>, ELENA KULESHOV <ek1...@att.com<mailto:ek1...@att.com>>, "SHAH, SANDEEP" <ss0...@att.com<mailto:ss0...@att.com>>, "TATTAVARADA, SUNDER" <sta...@research.att.com<mailto:sta...@research.att.com>>, "Nowak, Damian (Nokia - PL/Wroclaw)" <damian.no...@nokia.com<mailto:damian.no...@nokia.com>>, Krzysztof Opasiak <k.opas...@samsung.com<mailto:k.opas...@samsung.com>> Subject: RE:[onap-tsc] [Onap-release] [Maintenance Release]Status Update Hello, here's a quick report on last attempts on El Alto * A fix for Portal issue has been delivered and merged. We'll see on next dailies if it works (knowing that I'm OOO today and Morgan is back August 3rd) * e2e instanciation issues: - July 17th, 18th, 20th and 21th: issue on SO openstack adapter (https://gating-results.onap.eu/results/onap_daily_pod4_elalto-648089267/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D648089267_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw&s=KeYqnRR8LJK_Js8S-TXVLwdj_a-mpl1UaOoq6HDqQVE&e=>) --> partial logs sent to SO team but I forgot to retrieve the full logs :( - July 22th: issue on SDC onboarding (https://gating-results.onap.eu/results/onap_daily_pod4_elalto-650005168/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D650005168_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log&d=DwQF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw&s=dk7ufN9Tk3Jyj-N8GbHZ9B9c5-D_MvPOObniawf7UkE&e=>). I tried to restart but always the same issue - July 23th: Issue between SDC and SDNC (we don't see SDNC "ack" the reception of distribution) (https://gating-results.onap.eu/results/onap_daily_pod4_elalto-652346521/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D652346521_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log&d=DwQF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw&s=qsa4LJzl93jRDHAZip-h8GC8aa2g7Es3nx-5XtSzxiE&e=>). I tried to restart but always the same issue - July 24th: Issue on SDNC (preload data doesn't seems to be here but we have a 200 OK when uploading) (https://gating-results.onap.eu/results/onap_daily_pod4_elalto-654306232/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D654306232_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw&s=N5pCbrdUj3HPaq7a8yr2tBwFRWmBrCjPD3Pu1icMZaw&e=>). I tried to restart but always the same issue So e2e tests are quite buggy and fails at different steps, making it hard to debug. Regards, Sylvain ________________________________ De : Nowak, Damian (Nokia - PL/Wroclaw) [damian.no...@nokia.com] Envoyé : mercredi 22 juillet 2020 17:08 À : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>; DESBUREAUX Sylvain TGI/OLN; sylvain.desbureaux+...@gmail.com<mailto:sylvain.desbureaux+...@gmail.com> Cc : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> Objet : RE: [onap-tsc] [Onap-release] [Maintenance Release]Status Update Dears, Regarding the El Alto Maintenance Release, well, it`s definitely not ready... We`re observing the following issues in our test environment: 1. Portal is not responding to requests (we see it is unable to load externally defined roles to the internal Portal DB). We reinstalled Portal from the 5.0.1-ONAP tag, and the issue is resolved --> Means EL Alto MR Portal comes with a Bug. 2. APPC is not really working properly in El Alto MR (checked-out 2020-07-22). It looks like APPC is not really responding to calls from CDT, and it is not responding to calls from Swagger API UI. Are You observing these issues in Your test-systems too? I can understand, that not everyone is using APPC, but I think, quite anyone is using Portal... Rgds, Damian http://nok.it/onap<https://urldefense.proofpoint.com/v2/url?u=http-3A__nok.it_onap&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw&s=kBZ0Rb1OJzjW2NY5SbcZw1d6r1yl-RDHupnNQSiDrOI&e=> From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> On Behalf Of Sylvain Desbureaux via lists.onap.org Sent: Wednesday, July 22, 2020 11:40 AM To: Martial <gervais-martial.ngu...@intl.att.com<mailto:gervais-martial.ngu...@intl.att.com>>; onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> Cc: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> Subject: Re: [onap-tsc] [Onap-release] [Maintenance Release]Status Update Hi Martial, OK ! thanks for fast answer! Sylvain ________________________________ De : onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> [onap-rele...@lists.onap.org] de la part de Martial [gervais-martial.ngu...@intl.att.com] Envoyé : mercredi 22 juillet 2020 11:27 À : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> Cc : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> Objet : Re: [Onap-release] [Maintenance Release]Status Update Envoyé depuis mon smartphone Samsung Galaxy. Sylvain, As mentioned in the 'el alto' release note for CLAMP, The ELK stack is not part of the CLAMP el alto release due to the DMCA SEARCHGUARD issue. So it is normal that it is not coming up since it is not present. Br Martial Envoyé depuis mon smartphone Samsung Galaxy. -------- Message d'origine -------- De : "Lefevre, Catherine" <catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>> Date : 21/07/20 01:21 (GMT+01:00) À : Krzysztof Opasiak <k.opas...@samsung.com<mailto:k.opas...@samsung.com>>, sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>, dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>, onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>, onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> Cc : ranny.ha...@samsung.com<mailto:ranny.ha...@samsung.com>, DEBEAU Eric TGI/OLN <eric.deb...@orange.com<mailto:eric.deb...@orange.com>>, RICHOMME Morgan TGI/OLN <gervais-martial.ngu...@intl.att.com<mailto:gervais-martial.ngu...@intl.att.com>>, andreas-geiss...@telekom.de<mailto:andreas-geiss...@telekom.de>, krishna.moort...@wipro.com<mailto:krishna.moort...@wipro.com>, "PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN" <snaraya...@research.att.com<mailto:snaraya...@research.att.com>>, denghu...@huawei.com<mailto:denghu...@huawei.com>, seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>, onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>, onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> Objet : RE: [Maintenance Release]Status Update Thank you Sylvain. I agree we should pursue with the Frankfurt maintenance release. Can we finalize the release note? As soon as the release note will be available then I will officialize the Frankfurt maintenance release. Concerning the El Alto maintenance release, I would like to ask CLAMP/OOF and SO project teams to investigate the issues that you have identified. Many thanks & regards Catherine _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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 (#6946): https://lists.onap.org/g/onap-tsc/message/6946 Mute This Topic: https://lists.onap.org/mt/75721395/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
