17:00:39 <kopecmartin> #startmeeting qa
17:00:39 <opendevmeet> Meeting started Wed Nov 22 17:00:39 2023 UTC and is due to finish in 60 minutes.  The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:39 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:39 <opendevmeet> The meeting name has been set to 'qa'
17:00:48 <kopecmartin> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours
17:00:51 <kopecmartin> agenda ^
17:01:11 <lpiwowar> o/
17:01:29 <kopecmartin> let's get through the usual first
17:01:39 <kopecmartin> #topic Announcement and Action Item (Optional)
17:02:10 <kopecmartin> i'm gonna be on PTO next Monday and Tuesday .. I can't moderate the next office hour on Tuesday 15:00 UTC
17:02:57 <kopecmartin> we can either cancel or if frickler or lpiwowar want to host it we can do that too
17:03:38 <kopecmartin> i'll be back couple hours after the office hour so i can answer pings (if any) or vote on reviews that were brought up during the office hour
17:04:18 <lpiwowar> I don't mind moderating it but if frickler wants to host it then I think it should be him:)
17:04:41 <kopecmartin> let's discuss that tomorrow, it's late for frickler ;)
17:05:00 <kopecmartin> #topic Caracal Priority Items progress
17:05:00 <kopecmartin> #link https://etherpad.opendev.org/p/qa-caracal-priority
17:05:03 <lpiwowar> Ok
17:05:17 * kopecmartin checking if there any updates
17:08:33 <kopecmartin> gmann: seems like this can be abandoned
17:08:34 <kopecmartin> #link https://review.opendev.org/c/openstack/tempest/+/842240
17:08:44 <kopecmartin> the LP seems to be fixed
17:08:45 <kopecmartin> #link https://bugs.launchpad.net/nova/+bug/1960346
17:08:55 <kopecmartin> also the job seems to be passing
17:08:56 <kopecmartin> devstack-platform-centos-9-stream
17:09:01 <kopecmartin> #link https://zuul.openstack.org/builds?job_name=devstack-platform-centos-9-stream&skip=0
17:10:52 <kopecmartin> moving on
17:10:56 <kopecmartin> #topic Gate Status Checks
17:10:56 <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)
17:11:15 <kopecmartin> no patches there, anything urgent to review?
17:11:35 <lpiwowar> nothing from my side
17:11:45 <kopecmartin> #topic Sub Teams highlights
17:11:45 <kopecmartin> Changes with Review-Priority == +1
17:11:45 <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)
17:11:56 <kopecmartin> one patch here
17:11:58 * kopecmartin checking
17:12:33 <kopecmartin> +w
17:12:44 <kopecmartin> #topic Periodic jobs Status Checks
17:12:44 <kopecmartin> periodic stable full
17:12:44 <kopecmartin> #link https://zuul.openstack.org/builds?pipeline=periodic-stable&job_name=tempest-full-yoga&job_name=tempest-full-xena&job_name=tempest-full-zed&job_name=tempest-full-2023-1&job_name=tempest-full-2023-2
17:12:46 <kopecmartin> periodic stable slow
17:12:48 <kopecmartin> #link https://zuul.openstack.org/builds?job_name=tempest-slow-2023-2&job_name=tempest-slow-2023-1&job_name=tempest-slow-zed&job_name=tempest-slow-yoga&job_name=tempest-slow-xena
17:12:50 <kopecmartin> periodic extra tests
17:12:52 <kopecmartin> #link https://zuul.openstack.org/builds?job_name=tempest-full-2023-2-extra-tests&job_name=tempest-full-2023-1-extra-tests&job_name=tempest-full-zed-extra-tests&job_name=tempest-full-yoga-extra-tests&job_name=tempest-full-xena-extra-tests
17:12:54 <kopecmartin> periodic master
17:12:56 <kopecmartin> #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic
17:14:25 <kopecmartin> all seems fine although for some reason i can't load the last link
17:14:41 <lpiwowar> same
17:14:46 <kopecmartin> oh, it has just loaded, it took a long time :D
17:15:01 <lpiwowar> :D
17:15:10 <kopecmartin> tempest-full-test-account-no-admin-py3 still constantly failing
17:17:07 <kopecmartin> right, we've already filled an LP for this
17:17:10 <kopecmartin> #link https://bugs.launchpad.net/tempest/+bug/2043038
17:17:21 <lpiwowar> Yes, I was looking for it.
17:17:25 <kopecmartin> the failures are potentially related also to this one
17:17:26 <kopecmartin> #link https://bugs.launchpad.net/tempest/+bug/2020860
17:17:38 <kopecmartin> gmann: any luck on those?
17:18:43 <kopecmartin> moving on in the meantime
17:18:46 <kopecmartin> #topic Distros check
17:18:46 <kopecmartin> cs-9
17:18:46 <kopecmartin> #link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0
17:18:48 <kopecmartin> debian
17:18:50 <kopecmartin> #link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&job_name=devstack-platform-debian-bookworm&skip=0
17:18:52 <kopecmartin> rocky
17:18:54 <kopecmartin> #link https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx
17:18:56 <kopecmartin> openEuler
17:18:58 <kopecmartin> #link https://zuul.openstack.org/builds?job_name=devstack-platform-openEuler-22.03-ovn-source&job_name=devstack-platform-openEuler-22.03-ovs&skip=0
17:19:00 <kopecmartin> jammy
17:19:02 <kopecmartin> #link https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=0
17:19:21 <kopecmartin> all good \o/
17:19:36 <kopecmartin> #topic Open Discussion
17:19:36 <kopecmartin> anything for the open discussion?
17:20:04 <lpiwowar> I wanted to only quickly mention this launchpad
17:20:09 <lpiwowar> #link https://bugs.launchpad.net/tempest/+bug/1668690
17:20:19 <lpiwowar> It's about writing a test for a server evacuation.
17:20:42 <lpiwowar> The question is whether we want to write such a test in tempest as it would require to put a compute node to a fail state.
17:21:17 <lpiwowar> But if my understanding is correct then bringing a compute node to a fail state might mean that we won't be able to bring it back so it would probably be the only test we would be able to run.
17:21:57 <kopecmartin> also no other tests could run when this one would be being run
17:22:25 <lpiwowar> kopecmartin: +1 ... We might put it to the serial folder we created couple of months back. But it would probably not solve the issue.
17:22:26 <kopecmartin> well, the LP is 6 years old , it's not like anyone is missing this test case
17:23:04 <lpiwowar> So do you think that we should close it with wontfix?
17:23:45 <kopecmartin> and if it requires to put a compute node to a fail state, i wouldn't say it's something tempest can help with .. also putting the node to the fail state might be not 100% repeatable and that's not a good test case in general
17:24:34 <kopecmartin> let's get some other opinions on this, e.g. gmann ^,  and if more of us agree, then i would say yes
17:24:42 <lpiwowar> Yes, true. The last question maybe is whether there is a different way how to test this feature without bringing the compute node to a fail state. But I'm not sure about this.
17:24:53 <lpiwowar> kopecmartin: ack
17:26:03 <kopecmartin> #topic Bug Triage
17:26:03 <kopecmartin> #link https://etherpad.openstack.org/p/qa-bug-triage-caracal
17:26:26 <kopecmartin> i don't have any specific bug i could bring up :/
17:26:40 <kopecmartin> aand , that's all from my side
17:26:46 <kopecmartin> anything else?
17:27:24 <lpiwowar> Nothing from my side.
17:27:29 <kopecmartin> see you around then ;)
17:27:32 <lpiwowar> o/
17:27:34 <kopecmartin> #endmeeting