Tuesday, 2021-07-06

opendevreviewTakashi Kajinami proposed openstack/monasca-agent master: Revert "Replace fnmatch with oslo.utils.fnmatch"  https://review.opendev.org/c/openstack/monasca-agent/+/79958512:25
chaconpiza#startmeeting monasca13:01
opendevmeetMeeting started Tue Jul  6 13:01:35 2021 UTC and is due to finish in 60 minutes.  The chair is chaconpiza. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
opendevmeetThe meeting name has been set to 'monasca'13:01
adrianczHi13:01
chaconpizaHi adriancz13:01
chaconpizaThe agenda as usual https://etherpad.opendev.org/p/monasca-team-meeting-agenda13:02
chaconpizaLet's start13:03
chaconpiza#topic [Ceilometer Monasca Client] Lots of warnings and stack traces during test runs13:03
chaconpizahttps://bugs.launchpad.net/ceilometer/+bug/193422013:04
chaconpizacreated by Matthias Runge13:04
chaconpizaI investigated the issue13:05
chaconpizaand was able to reproduce it13:05
chaconpizaIn Ceilometer there are unittests related to Monasca, basically monasca-publisher, monasca-data-filter and monasca-client13:06
chaconpizaThe issue reported in Launchpad is from monasca-client13:07
chaconpizaThere are 8 unittest of Ceilometer's monasca-client13:07
chaconpizasome of these tests check scenarios with a mocked wrong response13:09
chaconpizafor example, unauthenticated user13:09
chaconpizaall those tests work ok. But of course the stacktracke of the exception is displayed in the output13:10
chaconpizaThis is what Matthias don't like13:10
chaconpizaWhat do you think Adrian?13:11
adrianczalso  I don't like this13:12
chaconpizaThe question, is it ok to display in the output of the tests stack traces of the mocked exceptions?13:13
adrianczi don't like this exception in the output 13:14
adrianczin my opinion this look ugly and sometimes is hard to read test result because of that.13:16
adrianczwe should see exception only when test fails13:16
chaconpizaCheck this unittest from Nova:13:17
chaconpizahttps://zuul.opendev.org/t/openstack/build/85f0fc646ca949a3a07649cc26dcb5df/log/job-output.txt13:17
chaconpizaLine No. 5190113:17
chaconpiza(It takes a little bit to load)13:17
chaconpizaCan you see that?13:18
adrianczyes, I can 13:19
adrianczi don't like this output13:19
chaconpizaSo, it is a similar situation: A mocked exception or mocked class that leads to the exception, as expected13:20
adrianczimagine this output  when you try to run tests in your local machine 13:20
adrianczand one test fail13:20
chaconpizaand then the test finishes with the  `{4} nova.tests.unit.network.test_network_info.NetworkInfoTests.test_hydrate [0.031209s] ... ok`13:20
adrianczand you try to search for exception 13:20
chaconpizaYes, I think this is the point of Matthias.13:21
chaconpizain the other hand, all unittests in OpenStack present this behavior13:21
chaconpizaI tried inside of the test to Try&Catch the exception and then Log some text about it. To replace the Traceback with the a Log file 13:23
chaconpizaBut, unfortunately without success.13:23
chaconpizaeven Try&Catch with general Exception and BaseException doesn't work.13:23
chaconpizaAdrian do you have any idea?13:24
adrianczat this pond I have no idea 13:24
adrianczi would need check the code 13:25
adrianczand play with this unit tests 13:25
chaconpizaI will take a look on the monasca-client unittests from the monasca-pythonclient repo. And compare them with the monasca-client unittests from the Ceilometer.13:26
adriancz+113:26
chaconpizaalright, anyways I will treat it with low priority, since nothing is really broken.13:26
chaconpizalet's move forward13:27
chaconpiza#topic [Monasca-Agent] Revert "Replace fnmatch with oslo.utils.fnmatch"13:28
chaconpizahttps://review.opendev.org/c/openstack/monasca-agent/+/79958513:28
adriancz+2 from me 13:29
chaconpizaBecause of some issues in PY2 with the standard fnmatch library, the oslo.utils.fnmach was used13:29
adrianczi think we should merge this 13:30
chaconpizaYes, I am agreed.13:30
chaconpizaSame change is on Ceilometer, Barbican, etc.13:31
adrianczdo we need to cherry pick this to stable branches ?13:32
chaconpizaI was thinking on that, because Wallaby, Victoria and Ussuri are PY3 only13:32
chaconpizaI will wait a little bit before to merge it into master, to see if somebody from the other projects complains on that change.13:33
*** osmanlicilegi is now known as Guest413:34
adrianczGood idea 13:35
chaconpizaBut I am almost sure that the change will be accepted.13:35
chaconpizaOk13:35
chaconpiza#topic Monasca Images Build (Stable Branches)13:35
chaconpizaHere as mentioned before, let's stop building everyday Train13:36
chaconpizaTrain is already in EM stage13:37
adrianczI agree 13:37
chaconpizahttps://review.opendev.org/c/openstack/releases/+/79075813:37
chaconpizaNo need to build it everyday13:37
chaconpizaBeside of the Train branch, we have issue in the other stable branches13:38
chaconpizaWallaby ,Victoria and Ussuri13:38
chaconpizaThe only one that is ok (with exception of Train) is Monasca-Notification13:39
chaconpizaLet's start to fix them, Adrian do you have any preference?13:40
chaconpizaPersister, Api, Agent, Common, etc...13:40
adrianczi think i can start with api or persister 13:41
chaconpizaAlright, take please persister I will take Api13:41
adrianczI think w should first check common 13:42
adrianczbecause all image depend on this 13:42
chaconpizaMonasca-Common is building ok from master branch13:42
adrianczperfect 13:42
adrianczOk, I will take persister 13:43
chaconpizapersister from master use as a base image monasca-common from master13:43
chaconpizapersister from Wallaby use as a base image monasca-common from master    too13:43
chaconpizapersister from Victoria use as a base image monasca-common from master    too13:44
chaconpizaetc...13:44
chaconpizathis is a second change we need to do after fixing the images:13:44
chaconpizapersister from Wallaby SHOULD use as a base image monasca-common from Wallaby 13:45
chaconpizaand so on13:45
chaconpizaok, those are all topic from the agenda13:46
chaconpizaDo you have any other topic to discuss today?13:46
adrianczNo 13:48
adrianczi have no topic 13:48
chaconpizaThen let's close the meeting13:48
chaconpizaThanks see you next week13:48
adrianczThanks Martin 13:48
adrianczbye 13:49
chaconpiza#endmeeting13:49
opendevmeetMeeting ended Tue Jul  6 13:49:32 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:49
opendevmeetMinutes:        https://meetings.opendev.org/meetings/monasca/2021/monasca.2021-07-06-13.01.html13:49
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/monasca/2021/monasca.2021-07-06-13.01.txt13:49
opendevmeetLog:            https://meetings.opendev.org/meetings/monasca/2021/monasca.2021-07-06-13.01.log.html13:49

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!