Running full would be fine - its really a startup confirmation issue since a restart of one of the dmaap containers can sometimes make the kafka/zookeeper stack go flacky - we never could figure out why or what was causing the read only condition so we added this test almost as a post-install validation that could be run on demand to check for that problem quickly versus waiting for a failed model distribution to find it.
brian -----Original Message----- From: morgan.richo...@orange.com <morgan.richo...@orange.com> Sent: Tuesday, September 1, 2020 10:20 AM To: fiachra.corco...@est.tech; onap-discuss@lists.onap.org; SAWANT, MANDAR <ms5...@att.com>; RAMESH, BHANU <bg6...@att.com>; UNNAVA, SUNIL <su6...@att.com>; FREEMAN, BRIAN D <bf1...@att.com>; LUNANUOVA, DOMINIC <d...@research.att.com>; conor.w...@ericsson.com Cc: DESBUREAUX Sylvain TGI/OLN <sylvain.desbure...@orange.com> Subject: Re: [onap-discuss] [ONAP [Dmaap] [healthcheck] questions on the dmaap healthchecks thanks Brian so is it OK to run DMaaP PubSub only one time (only in full for example) and exclude it from the other tests? note that the test is not always failing, so sometimes //zation is not a problem. we are running core/small/medium and full tags in // just to save CI time and detect issues due to //ization (on ONAP side..) core/small/medium/full corresponds to different scope of ONAP we used to triggered the End to End tests only if core Healthcheck were OK as we consider that core components MUST be all OK, components not in core are not so critical so even if some are FAIL we can try the end to end tests. running only full would be probably enough for the CI (only 47 tests) I can add a topic for next Integration weekly meeting to see if we keep only full and remove core/small/medium from the CI. /Morgan Le mardi 01 septembre 2020 à 13:04 +0000, FREEMAN, BRIAN D a écrit : > DMaaP PubSub test wasn’t designed to run in parallel. > > The test is confirming that Write's succeed since kafka get into a > mode where the REST API can read but not write to a topic. > > The test does a Get, then a Write of a message to a test topic and > then polls via Get till it sees the message or a loop counter is met > (failure). > The client queue used by robot is the same for every test (saves on > that problem of kafka not providing messages before a new client > connection) > > if you run it in parallel then likely only 1 will succeed since it > will remove all the messages from the topic (since it was read in > bulk) and the other clients wont see the message that was consumed by > the first client read/GET. > > It wouldn’t be that hard to change it to be parallelizable by making > the test client ID be unique to the test but this might have some > other affects since it will look like an ever growing number of > clients if you need to continuously run the PubSub test. > > So given that, why are we running it in parallel ? > > And we should definitely be running it for all size and particularly > full. > > Brian > > > > -----Original Message----- > From: onap-discuss@lists.onap.org <onap-discuss@lists.onap.org> On > Behalf Of Morgan Richomme via lists.onap.org > Sent: Tuesday, September 1, 2020 5:45 AM > To: SAWANT, MANDAR <ms5...@att.com>; RAMESH, BHANU <bg6...@att.com>; > conor.w...@ericsson.com; fiachra.corco...@est.tech; LUNANUOVA, DOMINIC > <d...@research.att.com>; UNNAVA, SUNIL <su6...@att.com> > Cc: DESBUREAUX Sylvain TGI/OLN <sylvain.desbure...@orange.com>; > onap-discuss@lists.onap.org > Subject: Re: [onap-discuss] [ONAP [Dmaap] [healthcheck] questions on > the dmaap healthchecks > > up > any comment from dmaap team? > > currently Health-Check . Basic DMAAP Message Router PubSub Health > Check is the only failing healthcheck test in daily frankfurt > small/medium healthcheck suites ( > https://urldefense.proofpoint.com/v2/url?u=https-3A__logs.onap.org_ona > p-2Dintegration_daily_onap-5Fdaily-5Fpod4-5Ffrankfurt_09-2D01-2D2020-5 > F03-2D09_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m > =z8kZKgLOF7FQ0pOCJTFw8otmhytXWA2F7E8wtoBOLf0&s=JVUDTDHXFR4xBEOHKj8zbYi > VXqFd6jkMU_q_Zyl6uwg&e= > healthcheck > Full results > medium or > small) > > And it is also failing in daily master (but only in small - it is Ok > in medium > https://urldefense.proofpoint.com/v2/url?u=https-3A__logs.onap.org_ona > p-2Dintegration_daily_onap-5Fdaily-5Fpod4-5Fmaster_09-2D01-2D2020-5F06 > -2D09_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=z8 > kZKgLOF7FQ0pOCJTFw8otmhytXWA2F7E8wtoBOLf0&s=sqJt7KIQOGwc55XkHNfLk8KQz9 > rDHBvV41HJmefcrW8&e= > > > could you help us to clarify dmaap healthcheck tests? > > thanks > > /Morgan > > > > Le jeudi 27 août 2020 à 10:07 +0200, Morgan Richomme a écrit : > > Hi, > > > > I recently noticed that the list of dmaap healthcheck tests is > > different according to the scenario core/small/medium and full > > healthchecks run in CI (see details below). > > the core/small/medium/health tags correspond to a > > minimal/small/medium/full installation. > > Dmaap tests are executed in all cases as it is part of a minimal > > installation. We run the HC in // > > > > I have 2 questions: > > > > 1) "Health-Check . Basic DMAAP Message Router PubSub Health Check" > > is > > not run in full, any reason? > > Could you list the dmaap healthcheck test we have to run (tests > > maintained). I will adapt te tags accordingly > > > > 2) "Basic DMAAP Message Router PubSub Health Check" > > this test is run 3 times in //, it seems that //zation can be a > > problem..1 test works weel, but seems to prevent the others. > > is there any restriction to play this test several times in //? > > If so we can play on the tag to execute it only once (full for > > instance) > > > > thanks > > > > Morgan > > > > > > If you look at the last run: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults. > > onap.eu_results_onap-5Fdaily-5Fpod4-5Ffrankfurt-2D705806202-2D08- > > 2D27- > > 2D2020-5F02-2D08_&d=DwIGaQ&c=LFYZ- > > o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgD > > mi2Fzw&m=z8kZKgLOF7FQ0pOCJTFw8otmhytXWA2F7E8wtoBOLf0&s=_UGejKMO6Neg > > uwK > > tdDY3F7aZ7br6VBoi4UfIvoUlCNg&e= > > > > core (tag core): 1 test KO ( > > https://urldefense.proofpoint.com/v2/url?u=https-3A__orange-2Dopenso > > ur > > ce.gitlab.io_-2D_lfn_onap_xtesting-2Donap_- > > 2D_jobs_705972817_artifacts > > _results_xtesting- > > 2Dhealthcheck_core_core_report.html&d=DwIGaQ&c=LFYZ- > > o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=z8kZKgLOF7FQ0pOCJTFw8o > > tmh > > ytXWA2F7E8wtoBOLf0&s=D_mlHg1mMONdVBxOSOD19gPesf8QMrPDzOCXoOn7syU&e= > > ) > > - Health-Check . Basic DMAAP Message Router Health Check > > - Health-Check . Basic DMAAP Message Router PubSub Health Check > > (KO) > > > > small (tag small): all tests OK > > - Health-Check . Basic DMAAP Message Router Health Check > > - Health-Check . Basic DMAAP Message Router PubSub Health Check > > > > medium (tag medium): 1 test FAIL ( > > https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults. > > onap.eu_results_onap-5Fdaily-5Fpod4-5Ffrankfurt-2D705806202-2D08- > > 2D27- > > 2D2020-5F02-2D08_xtesting-2Dhealthcheck_medium_medium_report.html- > > 23ta > > gs-3Fhealth-2Ddmaap&d=DwIGaQ&c=LFYZ- > > o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoM > > gDmi2Fzw&m=z8kZKgLOF7FQ0pOCJTFw8otmhytXWA2F7E8wtoBOLf0&s=qvRgX3hA9c > > Kvc > > dEHIp5SSxNb1IlRSJi4vJcJao5sPQ4&e= > > ) > > - Health-Check . Basic DMAAP Message Router PubSub Health Check > > (KO) > > - Health-Check . Basic DMAAP Message Router Health Check > > > > full (tag health): all tests OK ( > > https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults. > > onap.eu_results_onap-5Fdaily-5Fpod4-5Ffrankfurt-2D705806202-2D08- > > 2D27- > > 2D2020-5F02-2D08_xtesting- > > 2Dhealthcheck_full_full_report.html&d=DwIGaQ > > &c=LFYZ- > > o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=z8kZKgLOF7FQ0pOCJ > > TFw8otmhytXWA2F7E8wtoBOLf0&s=IEKkCy59lpc3Dc1NRjOY- > > ztqUSEQ9zMWfZvAlTM2a > > bQ&e= > > ) > > - Health-Check . Basic DMAAP Bus Controller Health Check With Basic > > Auth > > - Health-Check . Basic DMAAP Data Router Health Check > > - Health-Check . Basic DMAAP Message Router Health Check > > > > > > _____________________________________________________________________ > ____________________________________________________ > > 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 (#22020): https://lists.onap.org/g/onap-discuss/message/22020 Mute This Topic: https://lists.onap.org/mt/76446833/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
