Hi Santosh as far as I can see - the OOF deployment went wrong. No log in their stdout but as aaf-sms- preload job is FAIL, OOF deployment cannot be successful for sure. - init jobs failed we do not see the onap-dmaap-bc-post-install, which usually means that the installation took too long. it could explain also the error on the dev-aai-traversal-update-query- data job.
So I assume it is a problem of performance, it took too long and some jobs were not completed. OOM team will have a better view than me but what kind of Hardware are you using? The daily Frankfurt is using - 3 VMs for controllers (each VM: 4 core Go 10G disk) - 3 VMs ofr the etcd (on SSD disks) (each VM: 4 core Go 10G disk) - 12 VMs for the compute (16 cores / 24 Go of RAM 10 Go disks) A full ONAP is very greedy. It is possible to limit the scope and/or to increase some of the installation timer dependening on the kubernetes capabilities. /Morgan Last daily frankfurt: https://logs.onap.org/onap-integration/daily/onap_daily_pod4_frankfurt/09-29-2020_06-09/infrastructure-healthcheck/k8s/kubernetes-status/index.html Le vendredi 02 octobre 2020 à 17:45 +0900, Santosh Thapa Magar a écrit : > Hi mrichomme, > > Because of size limitation,I am sending you the logs of onap-k8s test > logs in three separate zip files in three different email. > This email consist of part 1 [onap-k8s-log1.zip] of the zipped logs. > > We would be grateful if you could have a look into it and suggest us > what to do next. > > Best Regards > Santosh Thapa Magar > > > -----Original Message----- > From: Santosh Thapa Magar <[email protected]> > Sent: Monday, September 28, 2020 6:49 PM > To: '[email protected]' <[email protected]>; > '[email protected]' < > [email protected]>; '[email protected]' < > [email protected]>; '[email protected]' < > [email protected]>; > '[email protected]' < > [email protected]> > Subject: RE: [onap-discuss] [Frankfurt] OOF Pods in Stuck Init State > > Hi mrichomme, > > Sorry for the delayed response. > We performed the Onap k8s test as per your suggestion. > However the test didn`t went well. > > Here is the snippet of the console output. > +--------------------------+---------------------+------------------- > --------+------------------+----------------+ > > TEST CASE | PROJECT | TIER | DURATION | RESULT | > +--------------------------+---------------------+------------------- > --------+------------------+----------------+ > > onap-k8s | integration | infra-healthcheck | 01:33 | FAIL | onap- > > helm > > > integration | infra-healthcheck | 00:38 | PASS | nodeport_ingress > > > | > > security | infra-healthcheck | 00:00 | SKIP | > +--------------------------+---------------------+------------------- > --------+------------------+----------------+ > > 2020-09-28 06:53:23,801 - xtesting.ci.run_tests - INFO - Execution > exit value: Result.EX_ERROR > > I have herewith attached the detailed console output[ONAP-k8s-test- > console-output.txt]. > Since the logs collected in /tmp folder is very big to send on > integration-team rocket channel and in mail, could you please let us > know which logs should be sent to you for your reference. > > We would be gratefuf if you could guide us the next step. > > Best Regards > Santosh Thapa Magar > > -----Original Message----- > From: [email protected] <[email protected]> On > Behalf Of タパマガルサントス > Sent: Wednesday, September 2, 2020 6:12 PM > To: [email protected]; [email protected]; > [email protected]; > [email protected] > Subject: Re: [onap-discuss] [Frankfurt] OOF Pods in Stuck Init State > > Hi Morgan > > Thank you very much for the suggestion. We will run the onap-k8s test > and share the results with you. > > Our environment`s helm and kubernetes version is as follows. > Helm : 2.16.6 > Kubernetes: 1.15.9 > > Best Regards > Santosh Thapa Magar > > -----Original Message----- > From: [email protected] <[email protected]> On > Behalf Of Morgan Richomme via lists.onap.org > Sent: Wednesday, September 2, 2020 3:29 PM > To: [email protected]; [email protected]; > [email protected]; > [email protected] > Subject: Re: [onap-discuss] [Frankfurt] OOF Pods in Stuck Init State > > Hi > > could you run the onap-k8s test and share the results to get a full > audit of your ONAP cluster? > > https://git.onap.org/integration/xtesting/tree/infra-healthcheck/README.md > > Can you also confirm the version of helm and kubernetes > > Thanks > > /Morgan > > > Le mercredi 02 septembre 2020 à 10:02 +0900, タパマガルサントス a écrit : > > Hi Aniello,Krishna > > > > Thank you very much for the suggestion. > > We confirmed the Music pods are all running and completed state. > > ubuntu@onap-rke:~$ kubectl get pods -n onap | grep music > > dev-music-5d46bcfbf8-mkbj8 1/1 Running 1 6d21h > > dev-music-cassandra-0 1/1 Running 1 6d21h > > dev-music-cassandra-1 1/1 Running 1 6d21h > > dev-music-cassandra-2 1/1 Running 2 6d21h > > dev-music-cassandra-job-config-8h78b 0/1 Completed 0 6d21h > > Could you > > help us what should we do next to fix this issue. > > > > Best Regards > > Santosh Thapa Magar > > -----Original Message----- > > From: [email protected] <[email protected]> On > > Behalf Of Aniello Paolo Malinconico via lists.onap.org > > Sent: Tuesday, September 1, 2020 3:58 PM > > To: Krishna moorthy <[email protected]>; > > [email protected] > > Subject: Re: [onap-discuss] [Frankfurt] OOF Pods in Stuck Init > > State > > > > I think they are into Init state, because the MUSIC pods are not > > into > > Running state. > > > > As Krishna said, check the music pods. > > > > Aniello > > _____________________________________________________________________ > ____________________________________________________ > > 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 (#22225): https://lists.onap.org/g/onap-discuss/message/22225 Mute This Topic: https://lists.onap.org/mt/76398452/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
