18:00:55 <gmann> #startmeeting qa
18:00:55 <opendevmeet> Meeting started Wed Jan 22 18:00:55 2025 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:55 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:55 <opendevmeet> The meeting name has been set to 'qa'
18:01:22 <gmann> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours
18:01:24 <gmann> today agenda ^^
18:01:33 <gmann> who all here today
18:01:40 <rlandy> o/
18:02:44 <gmann> rlandy: hi
18:03:23 <gmann> let's go through the regular items first and then we can discuss about devstack new plugin
18:03:27 <mtembo> Hello
18:03:35 <gmann> mtembo: hi
18:03:39 <gmann> #topic Announcement and Action Item (Optional)
18:03:42 <gmann> nothing for this weel
18:03:45 <gmann> week
18:03:58 <gmann> #topic Priority Items progress
18:04:10 <gmann> #link https://etherpad.opendev.org/p/qa-epoxy-priority
18:05:11 <gmann> there is no significant progress on items so we can check it next time
18:05:25 <gmann> #topic OpenStack Events Updates and Planning (Optional)
18:06:09 <gmann> no event planned in near future but we do have next cycle election coming
18:06:11 <gmann> #link https://governance.openstack.org/election/
18:07:05 <gmann> if there is no candidate for qa PTL role, we either go for DPL model or I will see if I can help as PTL role in next cycle
18:07:16 <gmann> #topic Gate Status / Fix Checks
18:07:26 <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)
18:07:51 <gmann> nothing is tagged as urgent fix but afaik I did not see any blocker here
18:08:09 <gmann> #link Changes with Review-Priority == +1
18:08:18 <gmann> #topic Changes with Review-Priority == +1
18:08:20 <gmann> #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)
18:08:40 <gmann> there is one review tagged as priority, I will check today
18:08:48 <gmann> #topic Periodic jobs Status Checks
18:09:08 <gmann> Periodic stable full:
18:09:10 <gmann> #link https://zuul.openstack.org/builds?pipeline=periodic-stable&job_name=tempest-full-2023-2&job_name=tempest-full-2024-1&job_name=tempest-full-2024-2
18:09:13 <gmann> all green here
18:09:30 <gmann> Periodic stable slow:
18:09:32 <gmann> #link https://zuul.openstack.org/builds?job_name=tempest-slow-2024-2&job_name=tempest-slow-2024-1&job_name=tempest-slow-2023-2
18:09:40 <gmann> Periodic extra tests:
18:09:51 <gmann> #link https://zuul.openstack.org/builds?job_name=tempest-full-2024-2-extra-tests&job_name=tempest-full-2024-1-extra-tests&job_name=tempest-full-2023-2-extra-tests
18:09:58 <gmann> Periodic master:
18:10:10 <gmann> #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic
18:11:05 <gmann> it seems tempest-full-test-account-no-admin-py3 job failing consistently
18:11:50 <gmann> Details: {'type': 'PolicyNotAuthorized', 'message': 'rule:create_network is disallowed by policy', 'detail': ''}
18:12:11 <gmann> some neutron rbac policy changed which we might need to check here
18:12:25 <gmann> I will try if I can find some time to debug it this week
18:12:51 <gmann> Distros check:
18:12:53 <gmann> Centos 9: https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0
18:12:53 <gmann> Debian: https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bookworm&skip=0
18:12:53 <gmann> Rocky: https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx
18:12:53 <gmann> Jammy: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&job_name=devstack-platform-ubuntu-jammy&skip=0
18:12:53 <gmann> Noble: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-noble&job_name=devstack-platform-ubuntu-noble-ovn-source&job_name=devstack-platform-ubuntu-noble-ovs&skip=0
18:13:24 <gmann> c9s job which is nv is failing some time which I can say not stable
18:14:22 <gmann> other job is ok, they are failing sometime but not consistently
18:14:41 <gmann> also, I will noble job from this list as we are now testing every job on Noble
18:15:12 <gmann> #topic Open Discussion
18:15:21 <gmann> rlandy/chandankumar: Ownership of prometheus devstack plugin (repo creation review will be sent after that). Context
18:15:26 <gmann> rlandy: please go ahead
18:15:29 <rlandy> thanks gmann
18:15:43 <rlandy> I think we pretty much have a suggestion
18:16:09 <rlandy> per sean-k-mooney and chandankumar's discussion
18:16:16 <rlandy> ""we can add the devstack, telemetry and watcher core groups to the plugin core group"
18:16:27 <rlandy> if there are no objections, we can go forward
18:16:36 <rlandy> gmann: ^^ you thoughts?
18:16:41 <gmann> I read the log
18:17:13 <rlandy> for recording ...
18:17:15 <rlandy> prometheus devstack plugin will be used by both telemetry and watcher projec
18:17:44 <rlandy> so ownership spreads teams
18:17:49 <gmann> first of all we have to understand what exactly meaning of adding a new project under QA.
18:18:23 <gmann> Every project (I will say subproject) under QA are maintained by their own core member team. Like tempest, devstack, grenade all have their own core group even some/many of them overlap with same people but idea if to maintained them by their team
18:18:54 <gmann> similar way if we add any devstack plugin, we need to have a separate plugin team to maintain it
18:19:49 <gmann> seeing it is related to devstack setup it is all ok to add it under QA project governance but ownership and maintaining responsibility needs to be taken care by this plugin team
18:19:58 <rlandy> (adding a bit more context): https://meetings.opendev.org/irclogs/%23openstack-qa/%23openstack-qa.2025-01-22.log.html ... I think the general understanding is that some combination of the two teams will look after it
18:20:31 <rlandy> but the general structure will be under QA
18:20:39 <gmann> for example, if plugin is active now and later we do not have any maintainer to maintain it then we might need to retire it as current QA team cannot maintaint it
18:20:48 <rlandy> understood
18:20:56 <gmann> This is same for all other devstack plugin
18:21:18 <gmann> rlandy: yeah, we create the core group from both project or any other project also
18:21:41 <rlandy> +1
18:21:47 <gmann> but my suggestion is to add a explicit list instead of adding watcher core or telemetry core group itself
18:22:23 <gmann> and this plugin list can grow if someone other than these two project show interest
18:22:31 <rlandy> I am not sure how the telemetry group is organized but we will pass on your recommendation
18:22:52 <rlandy> we are working closely with them now
18:23:05 <gmann> rlandy: yeah, maybe we can start with some of you there and then you can check if other member would like to join
18:23:10 <gmann> perfect than
18:23:20 <rlandy> ok - thank you gmann
18:23:53 <gmann> as next step, please start the repo creation and propose the governance change to add this under QA with separate group of maintainer
18:24:11 <gmann> please let me know if any help you need in that
18:24:35 <gmann> also, frickler is not here at this time but he can also give input on this
18:24:55 <rlandy> will do - this will start tomorrow
18:25:00 <gmann> I just ready his feedback in log so we all good here
18:25:06 <gmann> rlandy: perfect
18:25:09 <gmann> anything else
18:26:24 <rlandy> not from our side
18:26:50 <gmann> thanks rlandy and chandankumar
18:27:15 <gmann> I do not see any other topic in agenda, but I will keep it open for couple of min if anything else
18:29:20 <gmann> let's close if nothing else, thanks everyone for joining
18:29:24 <gmann> #endmeeting