14:00:10 #startmeeting qa 14:00:11 Meeting started Tue Sep 7 14:00:10 2021 UTC and is due to finish in 60 minutes. The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:11 The meeting name has been set to 'qa' 14:00:17 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 14:00:20 agenda ^^^ 14:00:24 hi all o/ 14:00:37 o/ 14:02:27 let's start 14:02:28 #topic Announcement and Action Item (Optional) 14:03:02 PTL Campaigning is ongoing 14:03:14 however for tempest there was just one candidate 14:03:16 me :) 14:03:34 #link https://governance.openstack.org/election/ 14:03:48 I don't have other announcements 14:04:06 #topic Xena Priority Items progress 14:04:07 o/ 14:04:15 #link https://etherpad.opendev.org/p/qa-xena-priority 14:04:19 any updates on these? 14:04:21 hi yoctozepto 14:04:31 hi kopecmartin 14:04:51 o/ 14:06:15 regarding tempest RBAC effort, I'd like to do a few experiments with tempest on a RBAC enabled system 14:06:39 is there a doc, which explains what options in local.conf need to be set in order to deploy? 14:06:47 i should probably know it 14:06:52 I think I have one job there but not merged 14:06:58 let me check 14:07:52 #link https://review.opendev.org/c/openstack/tempest/+/614484 14:07:59 I need to enable it more in tat 14:08:00 that 14:08:13 and devstack already run another job in gate 14:08:39 #link https://review.opendev.org/c/openstack/devstack/+/804263 14:09:09 devstack is more of just installation only. and tempest one will run test too but that need more work 14:09:52 thanks, i'll copy the config and will try to deploy on my local system so that i can debug tempest , see what's working and what's not 14:10:05 sure, +1 14:10:29 moving on 14:10:29 #topic OpenStack Events Updates and Planning 14:10:35 #link https://etherpad.opendev.org/p/qa-yoga-ptg 14:10:39 the etherpad for the PTG topics 14:10:46 I added a few topics there 14:10:51 feel free to add your proposals there as well 14:12:46 #topic Gate Status Checks 14:12:56 #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:13:01 any issues to bring up? 14:13:06 don't see any urgent patches 14:13:47 I am still working on patrole gate, network tests are passing. new image test start failing on policy change 14:14:08 volume and image test need fix and after that we can do release. I will spend time today on those 14:14:26 other than that I think no current gate issue 14:14:45 good, thanks 14:14:54 we'll do a major release, right, 29.0.0? 14:15:11 yeah, for tempest. and with tox.ini change etc 14:15:23 did you see anything we should wait for? 14:15:29 * gmann checking open patches 14:16:10 we might wanna decide what to do with the test_minimum_basic test 14:16:11 I do not find any so we are all good 14:16:29 i'll check too, but there isn't anything critical i think 14:16:34 kopecmartin: yeah but that can go later too. but anyways I am reviwing that 14:17:01 me too, i'll bring it up in a minute 14:17:04 #topic Periodic jobs Status Checks 14:17:09 #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-stable 14:17:14 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 14:17:21 all green \o/ 14:17:48 #topic Sub Teams highlights 14:17:53 any updates, highlights we need to discuss today ? 14:18:03 Changes with Review-Priority == +1 14:18:03 #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) 14:18:09 there are none 14:18:20 I wanted to bring up this 14:18:28 #link https://review.opendev.org/c/openstack/tempest/+/804107 14:18:48 i pinged also afazekas about it because i can't decide if i'm for or against .. 14:19:03 my main question is, is it safe to expand a functionality of that scenario test 14:19:03 ? 14:19:09 kopecmartin, Answered on the review. BTW you can ping me on this channel ;-) 14:19:23 afazekas: thanks 14:19:28 good to know, thank you :) 14:19:59 * kopecmartin reading the comment 14:20:18 cool, looks ok then 14:20:39 i wasn't sure if we can expect snapshot support on every environment the scenario test might be executed on 14:20:48 that was my main concern 14:21:15 as was also raised by sean-k-mooney 14:21:23 in the comments 14:22:11 kopecmartin: as you brought the config option for snapshot, I think it make sense to do it in separate test 14:22:14 commented in review 14:22:21 although i agree that creating a new test just for that is quite an overkill , it would be a duplication of that minimal test 14:22:23 kopecmartin, AFAIK the nova backand support is shrieked, not all backend supported it in the past . 14:22:52 kopecmartin: it does not need to be exact duplicate 14:23:33 we can just do 1. boot server 2. attach volume 3. write volume & snapshot 4. reboot server 5. check timestamp 14:23:46 but more or less doing most of part same 14:25:32 so I changed my vote now and going with the new test 14:25:58 so it would be basically TestMinimumBasicScenario just without security group work and of course plus the new additions (timestamp and snapshot) 14:26:24 yeah, I think most of scenario test need most of these steps except reboot 14:26:39 kopecmartin, https://docs.openstack.org/nova/latest/user/support-matrix.html "Attach block volume to multiple instances" makes it incompatble with the exotic drivers, the snapshot does not seams to increase the incompatibility 14:27:17 afazekas: that test doing volume snapshot via cinder API not server snapshot 14:27:50 but we do have config option for that to handle such incompatibility 14:28:20 gmann, yes, BTW,AFAIK the nfs is assisted snapshot, nova does extra loops with cinder 14:28:45 ah yes, that is true. 14:29:32 thank you for the good comments, i'm glad we sorted that out 14:29:33 #topic Open Discussion 14:29:43 * afazekas copied wrong action name, the good one "Attach block volume to multiple instances" 14:29:50 anything else to discuss? 14:30:30 meanwhile 14:30:31 #topic Bug Triage 14:30:35 kopecmartin: on release things 14:30:45 #link https://etherpad.opendev.org/p/qa-bug-triage-xena 14:30:47 gmann: oh, right 14:31:04 we need to check with release timing to start QA part on devstack/grenade etc 14:31:14 I can help on this if you need 14:32:00 yeah sure, when do we wanna start ? 14:33:12 I need to check the release timing on what step they are 14:33:45 I can check and push WIP sometime today or tomorrow 14:33:45 get it 14:34:08 and tempest release we want to do now or want to wait for the scenario test ? 14:34:33 I think we are good and can release with current hash 14:34:42 let's wait a little, if the patch gets updated soon, we can wait, if not let's move forward without it 14:35:03 ok, sure, we have time till 13th I think which is deadline 14:35:21 ok 14:35:28 but doing in this week will be good 14:35:34 agree 14:35:41 cool 14:36:07 ok then, anything else? 14:36:25 back to open discussion... 14:36:29 just one question: if you remember, devstack-plugin-ceph is now branched, but only starting from train; an upcoming change is going to break stein for sure, can we request a branch for stein too (probably starting from the branching point of train)? 14:39:32 i think we can, seems like we don't have a choice 14:39:33 tosky: sure, we can do if master is not working and EM of stable/stein team can work on that 14:40:17 gmann: after this change, it won't work for sure https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/807706 14:40:29 ok 14:40:30 can I simply propose the new branch to the release team, adding you all in cc? 14:40:44 +1, works fine 14:41:08 ack, thanks! 14:43:51 moving to bugs? 14:44:11 sure 14:44:13 #link https://etherpad.opendev.org/p/qa-bug-triage-xena#L5 14:44:23 i have recorded the nubmers as alwyas 14:44:30 i don't have anything else to bring up 14:45:35 yeah, did not see any critical bugs. 14:45:38 I am good too on this 14:46:56 ok, so it seems we're at the end 14:47:02 yeah 14:47:06 let's close the office hour then 14:47:08 thank you all 14:47:09 #endmeeting