Tuesday, 2021-08-03

*** jpena|off is now known as jpena06:54
*** rpittau|afk is now known as rpittau07:30
opendevreviewRajat Dhasmana proposed openstack/grenade master: Unblock Gate: create encryption type with right params  https://review.opendev.org/c/openstack/grenade/+/80331707:41
opendevreviewRajat Dhasmana proposed openstack/grenade master: Unblock Gate: create encryption type with right params  https://review.opendev.org/c/openstack/grenade/+/80331708:01
lyarwood^ can we get core grenade reviews on the above to unblock various gates?10:57
*** dviroel|out is now known as dviroel11:18
*** jpena is now known as jpena|lunch11:20
*** jpena|lunch is now known as jpena11:23
*** jpena is now known as jpena|lunch11:30
*** jpena|lunch is now known as jpena12:33
ykarelreview please https://review.opendev.org/c/openstack/devstack/+/80303913:50
gmannoffice hour time14:00
gmann#startmeeting qa14:00
opendevmeetMeeting started Tue Aug  3 14:00:37 2021 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'qa'14:00
gmannwho all are here today?14:00
yoctozepto\o/14:01
croelandto/14:01
opendevreviewElod Illes proposed openstack/devstack-gate master: Remove neutron-lbaas from PROJECTS list  https://review.opendev.org/c/openstack/devstack-gate/+/80334614:02
gmannlet's start14:03
gmann#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours14:03
gmanntoday agenda ^^14:03
gmann#topic Announcement and Action Item (Optional)14:04
gmannno announcement or AI from previous meeting14:04
gmann#topic Xena Priority Items progress14:04
gmann#link https://etherpad.opendev.org/p/qa-xena-priority14:04
gmannI have patch up for requirement to move tempest from u-c to blacklist file so that tempest master can be used for plugins job14:05
gmann#link https://review.opendev.org/c/openstack/requirements/+/78762114:05
jparolyo/14:05
gmannno other updates on rest of remaining Xena items14:06
gmann#topic OpenStack Events Updates and Planning14:06
gmann#link https://etherpad.opendev.org/p/qa-yoga-ptg14:06
gmannfor PTG, please start adding the topics you would like to discuss14:06
gmann#topic Gate Status Checks14:08
gmannwe have two failure to discuss today14:08
gmannone is grenade job failure 14:08
gmann#link https://review.opendev.org/c/openstack/grenade/+/80331714:08
gmannfrickler raising the question of backward incompatible change.14:09
abhishekkthis is blocking glance/cinder/nova and probably others as well14:09
croelandtyeah, this is blocking our RBAC work :/14:09
gmannIf i understand the original bug clearly, cinder change was done as bug fix instead of microversion14:09
gmann#link https://bugs.launchpad.net/cinder/+bug/192663014:10
gmannso the voluem create request fails later so new api checks are just an early failure?14:10
whoami-rajat__grenade doesn't check the encryption flow with barbican and also not with the failing drivers so it will never see that failure but it is still wrong from cinder standpoint14:10
whoami-rajat__cinder is just moving the async failure to a sync failure by moving the failing code from c-vol to c-api service14:11
gmannwhoami-rajat__: you mean the volume create request can pass ?14:11
whoami-rajat__for LVM, not for rbd nfs and probably other drivers14:11
gmannso back to frickler question, how they were passing before cinder change?14:11
gmannwhoami-rajat__: yeah that is difference14:11
gmannI remember we did that change in tempest test too for that reason14:12
gmannI am ok for the change as it is changing 4/5xx->400 only14:12
whoami-rajat__also how grenade is trying to create an encrypted volume type is not correct14:12
whoami-rajat__so it needs to be corrected anyway14:13
gmannwhoami-rajat__: anything else wrong other than passing cipher ?14:13
whoami-rajat__gmann, nothing as i remember, i can go through it again but for now my patch passes glance gate so it seems good14:14
opendevreviewyatin proposed openstack/devstack master: [DNM] Test c8-stream / fedora-latest with fixes  https://review.opendev.org/c/openstack/devstack/+/80314414:14
gmannwhoami-rajat__: ack thanks14:14
gmannfrickler: yoctozepto any comment on this how to proceed and unblock gate?14:14
opendevreviewyatin proposed openstack/devstack master: [DNM] Test c8-stream with reduced tempest concurrency  https://review.opendev.org/c/openstack/devstack/+/80314414:16
yoctozeptostill not understanding why it passed before14:16
yoctozeptono testing after request?14:16
gmannfor lvm which is default in grenade does pass but not other backend like barbican 14:16
gmannyoctozepto: in grenade yes, it just create it14:17
yoctozeptook, makes sense14:17
* yoctozepto approving14:17
gmannthanks, seems like frickler is not online now so let's unblock the gate and if any strong objection from him then we can continue discussion 14:18
gmannmoving to 2nd gate issue14:18
gmanncentos8 support and fix14:18
gmann#link https://review.opendev.org/q/I508eceb00d7501ffcfac73d7bc2272badb24149414:18
* yoctozepto approving rdo fix14:19
gmannwe have centos8 job fix and it work for victoria, you can see job green in victoria backport14:19
gmannyoctozepto: tricky thing here is how to fix centos8 in wallaby14:19
yoctozeptoyou mean stream-only?14:20
gmannyeah14:20
gmanncomment from yatin: "For wallaby need to use c8-strem job devstack-platform-centos-8-stream as RDO wallaby released only for c8-stream so may not work for c8"14:20
gmannas there is no wallaby release for centos8 so question is 1. how to fix it or 2. should we change centos8 to centos8-stream in wallaby ?14:21
yoctozeptoI would as it makes more sense support-wise14:22
gmannand wallaby testing runtime defined in TC is centos8 not centos8-stream so 2nd one is more tricky14:22
toskyjust to clarify: when I've advocated for exceptions on the list thread, I was suggesting to move all centos linux 8 jobs to centos stream 8 whenever an openstack release is still alive after centos linux 8 EOL14:22
yoctozeptoyeah14:22
gmannIMO, we should not change the stable runtime at this stage14:22
ykarelcentos8-stream is replacement for centos8, so would need to switch atleast when c8 goes EOL at year end14:23
ykareland would be better even before14:23
gmannykarel: yes we did in Xena14:23
gmannbut we should do in all stable branch or not that is bug question or work14:23
ykarelin puppet and tripleo have already switched to c8-stream 14:23
gmann*big14:23
gmannykarel: all stable also?14:23
ykarelgmann, for other stable c8 should work from RDO perspective as we support on both c8 and c8-stream14:24
ykarelbut wallaby+ only c8-stream14:24
ykareland this would change at year end when c8 goes eol14:24
gmannyeah so wallaby also changed right which is in questrion14:24
toskyykarel: what will happen to victoria after c8 EOL?14:24
gmanntosky: it still work with old c8 14:25
gmannas worked in devstack patch14:25
ykareltosky, i think repos will stale for C8 post EOL, i think it's currently being discussed14:25
ykarelso not have full context for that14:25
toskygmann: right now, but December is close :)14:25
ykarelso atleast there will be no update post December14:25
ykareland repos may exist for some time14:25
gmannso just curious, how c8 community migrate the customer using c8 for openstack victoria or wallaby?14:26
gmannykarel: tosky that is risky as you are going to delete the old released/used repo ?14:26
toskythat's what I'm trying to understand 14:26
ykarelc8 users will migrated to either c8-stream or rhel or any other rebuild of rhel14:26
gmannykarel: that seems a contract break if anyone has their production running on c8 with old openstack where it used to work and now might stop ?14:27
yoctozeptoyeah, I don't like the way it sounds14:28
gmannI do not know usage contract of c8 but still 14:28
yoctozeptoI am open to supporting Vicky on centos 8 stream though14:28
gmannyoctozepto: yeah, it seems very confusing for me and how migration is planned for old usage14:28
ykarelgmann, it should work with both c8 and c8-stream for supported releases14:28
ykarelthere were some announcement for it14:28
ykarelneed to fetch link14:28
gmannykarel: but you are saying at some time when repo are deleted then it might not work like currently for stable/wallaby14:29
toskybut technically centos 8 stream is not really different from the base one - just gets the updates first instead of later14:29
ykarelgmann, for stable/wallaby repos were never published for c814:29
ykarelit was c8-stream from beginning14:29
yoctozeptogmann: as tosky and ykarel say, it mostly works by replacing the repos and doing an update14:29
gmannykarel: ohk, then is it miss in our testing runtime?14:30
ykarelhttp://mirror.centos.org/centos/8-stream/cloud/x86_64/14:30
ykarelvs http://mirror.centos.org/centos/8/cloud/x86_64/14:30
yoctozeptogmann: it was announced late14:30
gmannohk14:30
gmannhow about this plan ?: 1. discuss in TC about updating the wallaby testing runtime to centos8-stream 2. accordingly QA proceed on changes.14:31
yoctozeptoI agree14:33
gmannthis is for stable/wallaby only but for victoria it is right fix and make c8 job green #link https://review.opendev.org/c/openstack/devstack/+/80307214:33
gmannso I am ok to merge the victoria fix14:33
gmannand wallaby one we can continue discussion as per above plan14:33
yoctozeptogmann: as need be, I am open to doing the same to Vicky as c8 goes eol before Vicky does14:33
gmannyoctozepto: I think we should not change victoria testing as it is changing the history and support. wallaby is fine as there is no way and centos8-stream announced in wallaby time but little later14:34
ykarelgmann, that fix can be merged in wallaby too14:35
yoctozeptogmann: well, technically it's the same distro, except for the delivery model14:35
yoctozeptoI'm just saying I'm fine with either going on stream14:35
yoctozeptoit's a weird situation but it's not that hard for us to adapt now that we support stream in CI14:35
gmannykarel:  that does not fix anything in wallaby, there is no c8-stream job there and c8 still failing. I would like to see some job running with that fix14:36
gmannyoctozepto: humm, not sure still. anyways let's discuss in TC how much backport we can do for c8->c8-stream14:36
ykarelgmann, actually the fix will be needed for any c8 release14:36
gmannykarel: confused. for wallaby c8 release?14:37
yoctozeptogmann: yeah, I would prefer we did not have to at all but life ain't easy this time of the century14:37
gmannsure. we can proceed as what TC decide on this. as QA we need to comply with defined runtime. 14:38
ykarelgmann, so the patch is specific to how rpm name is computed for c8, it's doing it's work in computing the correct name for wallaby and installing the rpm14:38
ykarelbut since the job there is c8, it's looking for wrong repo and fails14:39
ykarelbut okk if it's squashed with c8-stream job addition14:39
gmannykarel: yeah, let's wait for Thursday TC meet and then we can proceed on this.14:39
ykarelok Thanks14:40
gmannykarel: you would like to merge victoria one now? I am +2 on that and to merge before wallaby14:40
ykarelgmann, fine by me, it's unblocking some cinder jobs14:40
ykarelso should be ok to go with it14:41
gmannyeah please remove your -W14:41
gmannyoctozepto: what you say? https://review.opendev.org/c/openstack/devstack/+/80307214:41
ykarelremoving14:41
gmannthough we are skipping wallaby backport and merging vicrotia first but I think it is fine in this siutation 14:41
yoctozeptogmann: cherrypick id perhaps?14:41
gmannyoctozepto: ah yeah that can be updated. +114:41
yoctozeptoI am ok with the skip14:41
gmannykarel: ^^14:41
gmannk14:42
yoctozeptojust add the cherrypick metadata14:42
ykarelsure will update14:42
gmannthanks 14:42
yoctozeptook14:42
gmannany other gate blocker? 14:42
gmann#topic Periodic jobs Status Checks14:42
gmann#link https://zuul.openstack.org/builds?job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-train-py3&pipeline=periodic-stable14:42
gmann#link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic14:43
gmannall green here14:43
gmann#topic Sub Teams highlights14:43
gmannany updates, highlights we need to discuss for today ?14:43
gmannfrom subteam14:43
opendevreviewyatin proposed openstack/devstack stable/victoria: Fix Usage of rdo-release rpm  https://review.opendev.org/c/openstack/devstack/+/80307214:44
gmann#topic Gate Blocker Fix / Urgent Change14:44
gmann#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)14:44
gmannnothing here14:44
gmannI think we can merge this to about topic of gate status14:44
gmannas both are relevant and overlap 14:44
gmann#action gmann merge the two gate check topic into one14:45
gmann#topic Open Discussion14:45
gmannanything else to discuss by anyone which is not in agenda ?14:45
rosmaitajust want to say thanks for the work on getting centos-8 devstack build working in victoria14:46
eliadcohen+114:46
gmannrosmaita: +1, thanks to ykarel 14:46
rosmaitaykarel: ++14:46
gmannmoving next14:47
gmann#topic Bug Triage14:47
ykarelalso in noticed tempest tests random failures in master job, so trying out tempest concurrency reduce https://review.opendev.org/c/openstack/devstack/+/80314414:47
gmannykarel: ok, can you file a bug and how frequent it is? and which test14:48
ykarelgmann, sure will file14:48
gmannthanks14:49
gmann#link https://etherpad.opendev.org/p/qa-bug-triage-xena14:49
gmannbug report  ^^14:49
gmannno critical bug or other that what we already discussed 14:49
gmannthat is all from me today. any other bug we need to discuss? 14:49
yoctozeptonot from me14:49
gmannk14:50
gmannthanks all for joining. 14:50
gmann#endmeeting14:50
opendevmeetMeeting ended Tue Aug  3 14:50:22 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:50
opendevmeetMinutes:        https://meetings.opendev.org/meetings/qa/2021/qa.2021-08-03-14.00.html14:50
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/qa/2021/qa.2021-08-03-14.00.txt14:50
opendevmeetLog:            https://meetings.opendev.org/meetings/qa/2021/qa.2021-08-03-14.00.log.html14:50
rosmaitagmann: i was just reading through the scrollback14:50
rosmaitado you want to see a job run that uses https://review.opendev.org/c/openstack/devstack/+/803071 ?14:50
*** ykarel is now known as ykarel|away14:52
gmannrosmaita: we have devstack-platform-centos-8 in wallaby and if you see it is failing as this fix does not work for centos8 as no wallaby repo for centos814:52
rosmaitaright, so i have a cinderclient job that uses centos-8-stream for a devstack-based job14:53
gmannrosmaita: plan is to first check if we can update the wallaby testing runtime from cewntos8 to centos8-stream and then we can change the job t use centos8-stream in this fix14:53
gmannhttps://governance.openstack.org/tc/reference/runtimes/wallaby.html14:53
gmann^^ this still define centos8 and from Xena we started using centos8-stream14:54
gmannrosmaita: yeah, i know it work on centos8-stream as we see in master fix but which centos8 or centos8-stream to test in wllaby if in question14:54
gmann*is in14:54
rosmaitagotcha14:54
rosmaitaok, i will wait14:54
gmannin TC we will discuss about testing runtime doc update if we can do and then we can proceed14:55
rosmaitayeah, thanks for being willing to approve the victoria patch out-of-order14:55
rosmaitathat will get us unblocked for cinderclient gate14:55
gmann+114:57
*** jpena is now known as jpena|off15:06
*** rpittau is now known as rpittau|afk16:13
opendevreviewJames Parker proposed openstack/whitebox-tempest-plugin master: Add vgpu resize tests  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/79030416:23
opendevreviewyatin proposed openstack/devstack master: [DNM] Test c8-stream with reduced tempest concurrency  https://review.opendev.org/c/openstack/devstack/+/80314416:46
opendevreviewMerged openstack/devstack master: Updated from generate-devstack-plugins-list  https://review.opendev.org/c/openstack/devstack/+/80310017:20
*** dviroel is now known as dviroel|brb17:34
opendevreviewHuy Tran proposed openstack/tempest master: Remove container name from the list when container is deleted  https://review.opendev.org/c/openstack/tempest/+/80238818:05
opendevreviewMerged openstack/grenade master: Unblock Gate: create encryption type with right params  https://review.opendev.org/c/openstack/grenade/+/80331718:38
*** dviroel|brb is now known as dviroel18:42
clarkbfwiw I think frickler  is right with the -1 in ^18:43
clarkbgrenade exists to catch those problems and we should be careful overriding them18:43
bluesonicgmann and tempest cores: any chance I can get some reviews and possibly get approval for https://review.opendev.org/c/openstack/tempest/+/80238819:07
gmannbluesonic: ack, will check today19:08
bluesonicgmann: thanks! really appreciate it.19:09
gmannclarkb: grenade does not test that. it only create and see if create is successful  or not. but created volume type is not usable - https://bugs.launchpad.net/cinder/+bug/192663019:09
gmannwhat i understand from cinder change is - it is adding the api validation for early fail instead of current late fail so it is not actually changing any success case behavior 19:10
gmannrosmaita: ^^ correct me if I am wrong19:10
clarkbgmann: ok usually we make things span a release so that grenade doesn't have to change on the old side only on the new side19:12
clarkbif you have to chagne something that will break gernade you deprecate it, then n-2 upgrade to n-1 works. Then in n-1 you switch grenade to doing the new thing. THen grenade can upgrade n-1 to n19:13
clarkbhaving failures like this indicates that this was not done and potentially will result in user upgrade problems19:13
gmannclarkb: this is not case of change, it is fixing later fail to early fail. grenade does not test created volume type is actually created or usable or not. 19:14
gmannactually we did not test the broken case in grenade.19:14
gmannfor general upgrade change yes we do follow the deprecation process or at least change API via microversion and old one keep working with old version19:15
gmannif greande check 1. create volume type 2. use that 3. use created volume with that volume type then we could see if we actually broke upgrade or not. and these check could have catch the actual bug cinder fixed now19:16
gmannjust checking if volume type creation request is accepted or not is not complete upgrade testing 19:18
clarkbits not but it does indicate a chagne in behavior htat people may trip over and we have processes to avoid that19:21
clarkbbut I guess in this case you can't really deprecate the old behavior as it isn't something the user can opt itno19:22
gmannyeah that is why we can to change it as existing way of creating volume type is not any user has opted it as it fail later19:23
gmannso basically it is not backward incompatible behavior improving it to fast fail with api validation 19:24
opendevreviewMerged openstack/devstack-gate master: Remove neutron-lbaas from PROJECTS list  https://review.opendev.org/c/openstack/devstack-gate/+/80334619:30
opendevreviewMerged openstack/devstack-gate master: Retire django-openstack-auth  https://review.opendev.org/c/openstack/devstack-gate/+/80069319:30
rosmaitaclarkb: i think gmann has summarized the situation well19:52
opendevreviewGhanshyam proposed openstack/grenade master: WIP: testing  https://review.opendev.org/c/openstack/grenade/+/80339720:52
*** dviroel is now known as dviroel|out20:54
gmannbluesonic: thanks for explaining it in bug, now it is clear to me.21:05
gmannbluesonic: 1 comment to clear the list in class method delete_containers() https://review.opendev.org/c/openstack/tempest/+/802388/5/tempest/api/object_storage/base.py21:05
bluesonicgmann: thanks for the comments and suggestion. However, deleting in method delete_containers after L142 will not solve the race condition, and the change becomes unnecessary as the list is being re-initialized anyway. Can I make a copy of the list before L142, clear the list, and pass it in delete_containers() on L142? I can provide logs where the second test/method tearDown delete the container of first test/method. Hence, putting21:20
bluesonic the delete container name before all the condenses.21:20
bluesonicthat is, pass the copy of the list to delete_containers() on L142.21:23
opendevreviewGhanshyam proposed openstack/grenade master: WIP: testing  https://review.opendev.org/c/openstack/grenade/+/80339722:54

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