Hi Morgan, Thank you for sharing the results. Please find the details on the CLI health check issue below:
Issue: In CLI project, Currently we have fixed security issues and vulnerability issues and is delivered in the latest onap/cli docker image. And the CLI health check ROBOT script is updated (https://gerrit.onap.org/r/c/testsuite/oom/+/105573) to use HTTPS port, introduced in that latest docker image. We have tested health check of CLI locally, and is working fine. But I think in integration testing, latest CLI docker images is not used, so health check is failed with connection refused error as reported in results . Resolution: We have already submitted the OOM patch https://gerrit.onap.org/r/c/oom/+/104338 to enable fix provided for both security and vulnerability issues as part of OOM based ONAP deployment. So once this OOM patch is merged, CLI health check will pass automatically. And this patch is blocked by OOM team, who recommends to keep the CLI HTTPS certificate inside the OOM project similar to other projects like SO and other projects and document it for this release. So we are making the required changes in OOM project and testing is in-progress. Technically I feel, this patch could be merged and I could submit the new follow-up patch to address the OOM team recommendation. so I am waiting for OOM team inputs. Thank you Regards Kanagaraj Manickam Lead Architect Cloudfiy Networking OSDT Huawei Technologies India Pvt. Ltd. Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield Bengaluru-560066, Karnataka Tel: + 91-80-49160700 ext 72410 Mob: 9945602938 [Company_logo] ________________________________ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! From: [email protected] [mailto:[email protected]] On Behalf Of Morgan Richomme via lists.onap.org Sent: 15 April 2020 22:01 To: [email protected]; [email protected]; DEBEAU Eric TGI/OLN <[email protected]> Cc: Krzysztof Opasiak <[email protected]>; DESBUREAUX Sylvain TGI/OLN <[email protected]>; [email protected]; [email protected]; [email protected] Subject: [onap-ptl] [ONAP] [Frankfurt] Integration status for TSC meeting Hi summary of integration view for the TSC meeting (I will be off tomorrow) Daily Master results ********************* All the daily master run results can be seen on https://gating-results.onap.eu/results/ results of the day: https://gating-results.onap.eu/results/onap_daily_pod4_master-511390681-04-15-2020_06-04/ - onap-k8s OK (timeout on dmaap chart but it does not prevent to work) - all the healthcheck tests are OK except CLI - E2E use cases better (50% for PNF_registrate, basic-vnf OK on DT daily) - security -- jdpw OK -- public endpoints + MUSIC (patch in progress to fix it: https://gerrit.onap.org/r/c/oom/+/105038) + CLI (patch in the gate https://gerrit.onap.org/r/c/oom/+/104338 but no change since 1 week got 2x -2 from OOM) -- rooted pods + OOF (https://gerrit.onap.org/r/c/oom/+/103910) + CLI (https://gerrit.onap.org/r/c/oom/+/104338) + MSB (patch in the gate https://gerrit.onap.org/r/c/oom/registrator/+/104843 but also security issues, no update see recently) + MUSIC Issues fixed for CCSDK+SDNC and maybe MUSIC so tomorrow we should be under 20 M4/RC0 criteria ***************** so from a milestone perspective, we still have issues with some security bugs (due to M4) preventing an official RCO - for CLI. CLI was descoped for frankfurt but provided finally new code - security fixes - (which is good) but there are still security issues to be fixed - for MSB, I think there is a process issue https://gerrit.onap.org/r/c/oom/registrator/+/104843 is in gate but on a repository where we do not know who can merge as far as I understand this patch is needed to regenerate the dockers to update the helm chart..but until it is not merged, regeneration of the dockers is blocked. As Integration I do not want to merge OOM related patches (the supercommitter is not a very good idea and noone from OOM has this right). Here it is a patch impacing OOM, they shoudl have the +2 / merge - for MUSIC, patch is in progress (last update today) - for OOF, patch is in progress (last update 14th of April) RCO and use case testing ************************** regarding the RCO, the status is given here https://wiki.onap.org/display/DW/Frankfurt+Readiness+dashboard In this table we can see that almost all the projects provide their dockers now - MSB, MUSIC, OOF submitted code but it is not merged in OOM - CLI (as it got a NO GO) is not tracked in the table - CDS neither but their helm chart has not been merged yet: https://gerrit.onap.org/r/c/oom/+/102761 - Integration (robot pod) to be produced later (after integration phase) Beginning of next week we will deploy a frankfurt candidate in Windriver (OOM Master) SB-01 (2 weeks ago) and SB-04 (this week) have been already deployed as pre-frankfurt for pre-test I planned to go back to use case owners to say that it is time to test their use case on the futur frankfurt candidate. In // of the CI, Integration should also check the canonical vFW closed loop / scaleout / .. /Morgan _________________________________________________________________________________________________________________________ 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 (#6142): https://lists.onap.org/g/onap-tsc/message/6142 Mute This Topic: https://lists.onap.org/mt/73036009/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
