Tuesday, 2022-01-04

*** pojadhav|pto is now known as pojadhav05:02
*** akahat|PTO is now known as akahat06:02
*** akahat is now known as akahat|ruck06:30
opendevreviewDr. Jens Harbott proposed openstack/devstack master: Revert "Add option to set chap algorithms for iscsid for FIPS"  https://review.opendev.org/c/openstack/devstack/+/82330308:03
opendevreviewAndre Aranha proposed openstack/tempest master: Add support for ecdsa keys  https://review.opendev.org/c/openstack/tempest/+/80746508:38
opendevreviewAndre Aranha proposed openstack/tempest master: Add skip for tests that wont work under fips  https://review.opendev.org/c/openstack/tempest/+/81080808:38
opendevreviewAndre Aranha proposed openstack/tempest master: WIP - Refactor ssh.Client to allow other clients  https://review.opendev.org/c/openstack/tempest/+/82086008:38
*** bhagyashris_ is now known as bhagyashris08:45
opendevreviewRajat Dhasmana proposed openstack/tempest master: Fix: Schema validation of volume list detail  https://review.opendev.org/c/openstack/tempest/+/82337510:53
opendevreviewAndre Aranha proposed openstack/tempest master: WIP - Refactor ssh.Client to allow other clients  https://review.opendev.org/c/openstack/tempest/+/82086011:23
opendevreviewJiri Podivin proposed openstack/tempest master: Patch paramiko  https://review.opendev.org/c/openstack/tempest/+/82256011:38
opendevreviewJiri Podivin proposed openstack/tempest master: WIP - replace paramiko with libssh  https://review.opendev.org/c/openstack/tempest/+/80627411:38
opendevreviewJiri Podivin proposed openstack/tempest master: DNM - Add temporary link to patched paramiko  https://review.opendev.org/c/openstack/tempest/+/81080911:39
opendevreviewJiri Podivin proposed openstack/tempest master: TEST/DNM - add sleep in ceph tests  https://review.opendev.org/c/openstack/tempest/+/82027011:39
rpittaufungi: hi! About https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/821863 do you have any visibility on the availability of python 3.10 for ubuntu focal ?13:50
fungirpittau: https://packages.ubuntu.com/python3.10 indicates it hasn't made it into focal yet. coreycb (he's not in here but you can find him in #openstack-infra at least) may have details14:20
rpittaufungi: thanks! :)14:20
fungiyw14:21
kopecmartin#startmeeting qa15:00
opendevmeetMeeting started Tue Jan  4 15:00:17 2022 UTC and is due to finish in 60 minutes.  The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'qa'15:00
kopecmartin#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Weekly_QA_Team_meeting15:00
kopecmartinagenda ^^15:00
gmanno/15:01
vhario/15:01
frickler\o15:01
jelabarre-rho/15:02
kopecmartinwhat an attendance 15:02
kopecmartinhi there15:02
kopecmartinhappy new year to all :) 15:03
kopecmartinlet's go through the agenda15:03
kopecmartin#topic Announcement and Action Item (Optional)15:03
kopecmartinnothing here15:03
kopecmartin#topic Yoga Priority Items progress15:04
kopecmartin#link https://etherpad.opendev.org/p/qa-yoga-priority15:04
kopecmartinany updates here? 15:04
soniya29hello15:04
kopecmartinalthough i don't expect any due to holidays 15:05
soniya29kopecmartin, nothing from my side :)15:05
gmannI have been doing few microversion schema patches15:05
gmannbut need to check if they are good to review/passing zuul or not15:05
gmannother than that nothing much to share here15:06
kopecmartinnothing from my side either, i'm trying to catch up and go through mails and reviews 15:06
jelabarre-rhstill waiting for new patches to get incorporated that I then need to test15:06
kopecmartinack15:07
kopecmartin#topic OpenStack Events Updates and Planning15:07
jelabarre-rhand then maybe investigate my question on multiple-architecture coverage in Tempest (for what little I understand of the Tempest internals)15:07
kopecmartini was gonna bring that up in the open discussion 15:08
jelabarre-rhak15:08
kopecmartingood, let's quickly go through the usual and we'll be there in a minute15:09
kopecmartinregarding the events, nothing new15:09
kopecmartin#topic Gate Status Checks15:09
kopecmartin#link https://review.opendev.org/q/label:Review-Priority%253D%252B2+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade+OR+project:openstack/hacking)15:09
kopecmartinany gate failures to bring up?15:09
fricklergate was broken last week15:09
fricklerparamiko did a new release which broke rsa key login to cirros15:10
fricklerand u-c testing didn't catch this, because tempest deployed with committed u-c, not with the patch under test15:11
kopecmartinoh15:11
gmannyeah15:11
fricklerykarel did a fix for the latter and for now paramiko is capped15:11
kopecmartinthat's great15:11
fricklerI proposed a fix for tempest https://review.opendev.org/c/openstack/tempest/+/82315915:12
fricklerbut there's also other options like switching to ecdsa possibly15:12
kopecmartinthe DNM in the title confuses me15:12
gmannswitching to ecdsa is in progress i think in tempest15:12
kopecmartingmann:  if you mean this15:13
kopecmartin#Link https://review.opendev.org/c/openstack/tempest/+/80746515:13
gmannyeah15:13
kopecmartinit's more like adding a support, not switching 15:13
fricklerkopecmartin: I went for DNM because I wanted to discuss whether to do this unconditionally or add a tempest flag15:13
gmannyeah after support we will be able to switch in devstack15:13
kopecmartinand i think it's ready , it's the first piece required in order to move closer to fips  goal15:13
fricklermedium term I'm also hoping to get a new release of cirros done that fixes the issue properly15:14
frickleror possibly finally get along with forking cirros15:14
gmannfrickler: do you have testing patch for 823322 ?15:14
fricklergmann: no, since you don't see the issue in CI. I tested locally15:15
gmannok15:16
kopecmartinI'd go with https://review.opendev.org/c/openstack/tempest/+/807465 15:17
gmannfrickler: kopecmartin lgtm, +215:17
fricklerthen we merged the openeuler patch and almost immediately broke it with the fips patch15:17
kopecmartinit would help us to bypass the gate failure and test the esdsa support even more15:18
kopecmartinas devstack would switch as gmann mentioned15:18
fricklerand finally mlavalle has a fix up for fedora which is important for neutron testing https://review.opendev.org/c/openstack/devstack/+/82321815:20
gmannyeah, slaweq just pinged for review. I will also check after meeting15:20
fricklerI added the same swap workaround as we have for other platforms already15:21
gmann+215:22
gmannon stable/train Tempest pin. Tempest 28.0.0 pin is reverted to unblock gate. I will continue working on finding the compatible Tempest version for stable/train/ currently master is used and gate is green.15:22
kopecmartinyeah, on that i thought stestr version was the issue15:24
gmannhumm. trackback was from tempest run command not stestr so I am not 100% sure15:25
kopecmartinthe version of stestr which was used didn't have the new args for sure, i checked the stestr's repo manually 15:26
gmanntempest 26.1.0 has exclude-regex arg in tempest run command but it gave error when job passing it and even help message of tempest run does not show new arg15:26
kopecmartinthat was strange yes15:26
gmannkopecmartin: yeah but in that case tempest run should accept the new arg and stestr should raise error15:26
gmannyeah, something strange there. I will check this week.15:27
kopecmartinoh, that's right, tempest has a try except block for that situation , hmm15:27
kopecmartinok, thanks15:28
kopecmartinmoving on15:28
kopecmartin#topic Periodic jobs Status Checks15:28
kopecmartin#link https://zuul.openstack.org/builds?job_name=tempest-full-xena-py3&job_name=tempest-full-wallaby-py3&job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-train-py3&pipeline=periodic-stable15:28
kopecmartin#link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic15:28
kopecmartinseems all good here15:28
kopecmartin#topic Sub Teams highlights15:28
kopecmartinChanges with Review-Priority == +115:29
kopecmartin#link https://review.opendev.org/q/label:Review-Priority%253D%252B1+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade+OR+project:openstack/hacking)15:29
kopecmartinthere are 4 patches, i've reviewed 2 already, the rest I'll try check later today15:29
kopecmartinany changes to bring up?15:29
kopecmartin#topic Open Discussion15:32
kopecmartin(gmann) Turning off the openstack-health service and so does retirement of it? 15:32
kopecmartinwe've got a volunteer 15:32
kopecmartinlet me find the email15:32
gmann+115:33
kopecmartinI summarized what we talked about on the openstack-health meeting before holidays15:33
kopecmartin#link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026487.html15:33
jelabarre-rhArx Cruz?15:33
gmannyeah15:33
kopecmartinso any recommendations where to start? 15:34
gmannI think we have repo maintainer now so let's allow them to fix the current issue and once it is up then we will discuss on hosting issue 15:34
gmannkopecmartin: it will be good to fix it and bring it up http://status.openstack.org/openstack-health/#/15:35
gmann#luink http://status.openstack.org/openstack-health/#/15:35
gmann#link http://status.openstack.org/openstack-health/#/15:35
arxcruzkopecmartin: yo 15:35
gmannarxcruz: hi15:35
arxcruzgmann: congrats on the new heir :) 15:35
gmannthanks :)15:35
gmannarxcruz: thanks for volunteering on maintaining the o-h.15:35
arxcruzsure 15:36
gmannarxcruz: as you might know we have two issues/things here. 1. maintain repo 2. hosting infra15:36
gmanncurrently dashboard is broken #link http://status.openstack.org/openstack-health/#/15:36
arxcruzgmann: yes, as I understood, rdo will provide the infra right ?15:36
arxcruzwe can maintain 15:36
gmannlet's fix that as first step and then we can talk about hosting infra need or so15:36
arxcruzgmann: sure, actually, it's because there is no data being populated 15:37
gmannarxcruz: infra is not yet solved. we will see if upstream infra can be used from new aws credits for e-r or so15:37
arxcruzok 15:37
arxcruzfrenzy_friday: what's the url for our o-h ?15:37
gmannarxcruz: yeah, I have not checked it but something wrong in code?15:37
gmannfrenzy_friday: #link http://status.openstack.org/openstack-health/#/15:38
arxcruzgmann: so, i can tell in our case, there's a html site, that is the status.o.o/o-h 15:38
gmann#link https://opendev.org/openstack/openstack-health15:38
gmann^^this is source code15:38
arxcruzand also a backgorund job that do some queries on the logs15:38
arxcruzand create a json file 15:38
arxcruzthis background job runs every x hours 15:38
arxcruzand write down a json file that the website reads and shows the results15:39
arxcruzin our case, we create a new branch on openstack-health, because our elasticsearch was newer and we had to make changes in the code for the new api's 15:39
gmannso fixes can be in existing repo right? #link https://opendev.org/openstack/openstack-health15:40
arxcruzgmann: yes, in a branch called rdo 15:40
gmanndid not get?15:41
gmanno-h repo is branchless and we do not tag also. like doing /using it from master version itself15:41
arxcruzgmann: https://opendev.org/opendev/elastic-recheck/src/branch/rdo15:41
gmannohk you mean e-r one15:42
gmanni got confused with o-h repo15:42
arxcruzgmann: yeah, sorry, my mistake15:42
arxcruzi just come back from vacation, not 100% yet on all the details :) 15:42
gmannsure, we can discuss those later. but brining it up will be good first step and to check for infra need15:43
gmann*bringing dashboard up 15:43
kopecmartinI'll try to look more into it with arxcruz and let's see what we'll come up with 15:45
kopecmartinwill share next week15:46
gmannand we can keep this topic in agenda for infra things or so15:46
gmannthanks again arxcruz 15:46
kopecmartin+115:46
kopecmartinanother topic in the agenda is15:46
kopecmartinabout expanding devstack team with potential candidates15:46
kopecmartinany updates here?15:46
arxcruz:)15:46
gmannah, forgot about it, I will do this week15:46
gmannno further updates on this15:47
kopecmartinok :) 15:47
kopecmartinthen we have the mixed-architecture stack topic15:47
kopecmartin#link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026492.html15:47
kopecmartinI was thinking about adding a new opt in tempest which would skip tests which are not meant for different architectures 15:48
gmanndo we need test changes for that? or just run the tests with different image in separate job?15:48
kopecmartinthe same opt could be then used for tests which are specific to those architecture 15:48
gmannkopecmartin: skip is not good IMO, if those operation perfoermed by tests cannnot be done in real also then just do not run the test15:49
gmannif they can be done then we need to adjust the tests15:49
kopecmartinyeah, makes sense, .. then maybe let's start from a job, let's create a job with different arch and let's see what's failing and we can take it from there15:49
jelabarre-rhI'm thinking in terms of a system where there might be multiple architectures mixed together.  15:50
gmannyeah, and that will be good feedback to projects that this operation did not work in this arch so you will fix it or add as a known limit?15:50
gmannjelabarre-rh: you mean mixed compute node?15:51
jelabarre-rhyes15:51
gmannand if tempest test end up creating VM on differrent arch compute node15:51
jelabarre-rhthere is a customer running x86_64 and ppc64le within the same stack15:51
fricklerbefore starting to mix things, how about finishing up the arm devstack job and getting it working?15:51
gmannin that case, challenge is how to detect those mixed arch in tempest/15:52
gmannTempest is API driven test suits and not aware much about underlying arch15:52
gmannfrickler: +115:52
jelabarre-rhI know IBM Power ends up stopping at Train (long story), but I expect the same thing may happen for ARM and maybe RISC-V15:52
jelabarre-rhI'm bringing it up now so planning can happen before such systems need to be tested15:53
jelabarre-rha discussion topic rather than an urgen current need15:53
gmannyeah, but for tempest it is difficult to know which compute node where test VM is schedule to boot is of what arch15:54
kopecmartina good ptg topic, i'll make a note of it somewhere 15:54
gmannTempest being as a user of OpenStack, should not aware of compute node arch. for example, if user boot/migrate  VM on mixed arch then what happen? what are SLA from provide side15:55
gmannbecause user operation may fail on mixed arch right?15:56
jelabarre-rhit would be more than just testing one arch then the next, as you'd want to have Affinity and Migration check *how* an attempt to migrate an instance between architectures fails15:57
gmannjelabarre-rh: so that is expected behavior right? I mean if user perform those, it fail.15:58
jelabarre-rhright15:58
gmannso test failing there give the right results. instead skipping test can just hide the things15:59
jelabarre-rhI happened upon that more by chance, because I'm mainly testing mixed-architecture deployment, and not running Tempest against x86_64, just ppc64le/15:59
gmannk16:00
gmannI think we are running out of time. I am +1 to discuss in PTG more.16:00
gmannor next meeting16:00
kopecmartinyup16:01
gmannbut as first step, having job and see what all fail will be good input for discussion16:01
kopecmartinagree16:01
jelabarre-rhsounds good.   Mainly to brainstorm for future revisions16:01
kopecmartin#topic Bug Triage16:01
kopecmartin#link https://etherpad.opendev.org/p/qa-bug-triage-yoga16:01
kopecmartinbug numbers are recorded at ^16:01
kopecmartini have this one fix to share16:02
kopecmartin#link https://review.opendev.org/c/openstack/tempest/+/82337516:02
kopecmartinthat's all from my side 16:02
gmannkopecmartin: ack, will check schema one16:02
kopecmartinthanks16:02
kopecmartinthank you all16:03
kopecmartinsee you around16:03
gmannthanks kopecmartin 16:03
kopecmartin#endmeeting16:03
opendevmeetMeeting ended Tue Jan  4 16:03:18 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:03
opendevmeetMinutes:        https://meetings.opendev.org/meetings/qa/2022/qa.2022-01-04-15.00.html16:03
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/qa/2022/qa.2022-01-04-15.00.txt16:03
opendevmeetLog:            https://meetings.opendev.org/meetings/qa/2022/qa.2022-01-04-15.00.log.html16:03
soniya29thanks kopecmartin 16:04
clarkbarxcruz: gmann: personaly considering how long it hsa been broken with no one noticing or complaining I think you should seriously consider turning it off instead. I think it being unnoticeable for so long is a good indication it isnt well used and that continued maintenance is unlikely16:47
clarkbmy takeaway from the call with RDO was basically that there wasn't anothe rgroup that needed this tool and need is a good driver for maintenance16:47
clarkbif there was a shared need then that could have been leveraged but there wasn't16:47
arxcruzclarkb: hmm... we do use, not specifically the part that gmann is interested, but we do use, and help us a lot, that's the reason we are running our own rdo version of it 16:49
arxcruzit would be nice to have subunit2sql and tempest data16:49
arxcruzbut it helps our work on tripleo 16:49
clarkbno you don't use it, that was the result of the call we had16:50
clarkbyou use elsatic-recheck which is completely different16:50
clarkbdon't confuse the two things16:50
arxcruzclarkb: ok 16:50
arxcruzmaybe I am indeed confusing :) 16:50
clarkband no one hsa used this for about 6 months or however long it has been broken16:51
clarkbwhich is why I make this recommendation16:51
arxcruzok16:52
clarkbarxcruz: the result of th emeeting with RDO was that RDO has its own tooling and doesn't need the per test case resolution. Also if I interpreted correctly the need of subunit was felt to be problematic because not everything uses subunit16:56
clarkbthe elastic-recheck and elasticserach stuff is separate and has ongoing maintenance via an opensearch donation from amazon and work from dpawlik to convert ingestion of logs to something that happens outside of the zuul base job16:57
arxcruzclarkb: yeah, right now we don't run too much tempest tests in our tests due the lack of time/resources 16:57
clarkband that is what RDO has been using and helping with and I don't see that changing16:57
arxcruzclarkb: ok I understand now, I wasn't on the RDO meeting 16:57
arxcruzthanks for the clarification 16:58
gmannclarkb: arxcruz yeah, triopleo does not use it. but if we can bring it up and running then we can discuss on usage vs infra need for this dashboard to keep it up17:03
clarkbgmann: I'm suggeting that the lack of interest for th elast 6 months is a good indication that we shouldn't bother17:04
gmannarxcruz volunteer to maintain it so I am ok to hold the retirement and if he thinks it is not much usable then we can retire17:04
clarkbwe can put effort into it but if no one is using it for 6 months is that a good investment17:04
clarkbgmann: I also think arxcruz didn't understand what it was they were volunteering for and confused it with the ELK stuff17:04
arxcruzclarkb: yeah, you're right, but doesn't mean i can't do the o-h as well :) 17:05
arxcruzin our case specifically, we don't use because we run only a small set of the tempest tests17:05
arxcruzbasically the basicnetworkscenario 17:05
arxcruzand specific tests on jobs that have specific services enabled 17:05
gmannfrom ML and today discussion i think arxcruz is going to maintain the o-h. he was confused with o-h being used in tripleo17:05
arxcruzso, when a job fails, it's easy to spot 17:05
gmannbut yes, I am ok with both option retire or fix but its arxcruz CALL17:06
gmanncall17:06
arxcruzgmann: if you need me I'm here to help :) 17:06
arxcruzif it is something that will help, i'm more than happy to help 17:06
gmannarxcruz: I will say your call :) because i cannot help in that and also do not use much. 17:07
gmannlast time before you volunteer, we decided to retire it as no one there to maintain it who need it so let's retire repo itself17:07
arxcruzok, i'll talk with kopecmartin tomorrow and we will discuss this better ok ?17:07
gmannsure. if you or anyone use it or helpful then you or they maintain then we will not force it to retire17:08
arxcruzok17:08
gmannas repo retirement i mean. infra hosting is another things to discuss with clarkb or in TC17:09
clarkbright from a service perspective I have a strong desire to turn it off because no one is using it17:09
clarkbin my opinion it would be a bda investment ot resurrect something unused for 6 months with no one saying they need the tool17:10
gmannyeah. let's wait for arxcruz call to use/maintain it now. but yes for 6 months it has not been used as it was broken.17:10
clarkbthe ELK situation was different. Multiple people said it was important and useful and we figured out a way forward. But I'm not seeing that with o-h17:11
opendevreviewMerged openstack/devstack master: Fix stacking without preconfigured DATABASE_PASSWORD  https://review.opendev.org/c/openstack/devstack/+/82281918:33
opendevreviewMerged openstack/devstack master: init_cinder() shouldn't always create DEFAULT_VOLUME_GROUP_NAME  https://review.opendev.org/c/openstack/devstack/+/55583618:50
mtreinishgmann: what is needed on o-h? Just saw the ping18:58
opendevreviewMerged openstack/tempest master: Fix: Schema validation of volume list detail  https://review.opendev.org/c/openstack/tempest/+/82337519:23
opendevreviewMerged openstack/devstack master: Fix mysqladmin failure for Fedora 34 and mariadb  https://review.opendev.org/c/openstack/devstack/+/82321819:24
*** tosky_ is now known as tosky20:32
gmannmtreinish: it is down, not sure if it is code issue or hosting one? so we need two things 1. someone to maintain source code for bugs 2. we need to find infra resources for this services which we can discuss in TC once we are sure that someone is there to maintain the repo. 21:42
gmannit been ~ 6 month it is down 21:42
mtreinishgmann: it looks like the subunit2sql db is missing data. The runs and test_runs tables are empty22:07
mtreinisho-h itself is pretty minimal it just proxies queries to subunit2sql and es. Keeping those things running is much more important22:08
mtreinishthe place we o-h needs the most work is the js side of it, the ui is a bit clunky and I'm sure 50% of the 20k npm dependencies that get pulled in have security issues or something22:11
gmannyeah, js part is something for which we do not have anyone in QA right now who can take care (just keep it up)22:14
mtreinishgmann: I'm about EoD now, but I can check with clarkb and fungi tomorrow to see if there is anything in the logs about subunit2sql. My guess is that a dependency update for sqlalchemy or oslo* or something broke the population of new results (assuming the workers are still running) and the prune job has progressively been removing old results22:18
gmannmtreinish: sure, thanks. arxcruz volunteer to help for maintaining o-h. He can also help in debugging. but thanks for looking 22:19
mtreinishyeah, just ran recheck on some open patches on gerrit. It looks like there are definitely some sqlalchemy compat issues with newer versions. Not sure if they're the issue or not, but it definitely needs to be fixed22:34
mtreinishthe simple workaround is probably to just pin the sqlalchemy version on the worker nodes while we wait for a fix in subunit2sql22:36
fungithat's probably doable in the configuration management for it, if that's not also bitrotted22:47
fungior we could temporarily disable configuration management for those two servers temporarily and downgrade sqla on them i guess22:47
fungibut yeah, this week is not great for me, at least not prior to, say, friday23:14
fungii'm buried under end-of-year/start-of-year paperwork23:14

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