13:00:33 <mnasiadka> #startmeeting kolla
13:00:33 <opendevmeet> Meeting started Wed May 31 13:00:33 2023 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:33 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:33 <opendevmeet> The meeting name has been set to 'kolla'
13:00:37 <mnasiadka> #topic rollcall
13:00:38 <mnasiadka> o/
13:01:05 <frickler> \o
13:01:06 <mattcrees> o/
13:01:17 <mmalchuk> q/
13:01:17 <SvenKieske> o/
13:01:17 <ramona-beermann[m]> o/
13:01:17 <mhiner> o/
13:01:40 <mmalchuk> o/
13:01:56 <bbezak> o/
13:03:20 <mnasiadka> #topic agenda
13:03:20 <mnasiadka> * Announcements
13:03:20 <mnasiadka> * CI status
13:03:20 <mnasiadka> * Release tasks
13:03:20 <mnasiadka> * Regular stable releases (first meeting in a month)
13:03:21 <mnasiadka> * Current cycle planning
13:03:21 <mnasiadka> * Additional agenda (from whiteboard)
13:03:23 <mnasiadka> * Open discussion
13:03:26 <mnasiadka> #topic Announcements
13:03:44 <mnasiadka> First of all, kolla/kolla-ansible/ansible-collection-kolla and kayobe have had their antelope (2023.1) rc1
13:04:24 <mnasiadka> second - I'm off for the next week, and then in two weeks from now I'm in Vancouver for OpenStack Summit
13:05:01 <mnasiadka> bbezak has agreed to host the weekly meetings, unless you agree those are not required - then we can cancel them
13:05:46 <mnasiadka> #topic CI status
13:06:17 <mmalchuk> not really required, but reviews postponed for three weeks (at least in kayobe) :(
13:06:21 <mnasiadka> I think it's green-ish, not counting some cephadm-upgrade jobs that I'm trying to fix
13:07:02 <mnasiadka> #topic Release tasks
13:07:31 <mmalchuk> not. CI zed and yoga broken due baremetal deploy problems in rl9
13:07:53 <mmalchuk> related fix: https://review.opendev.org/c/openstack/kayobe/+/883727/2
13:08:49 <mmalchuk> kayobe only
13:09:02 <mnasiadka> why oh why this patch didn't have review priority
13:09:11 <mnasiadka> and why it's not written on the kolla whiteboard
13:09:14 <mnasiadka> well, added RP+2
13:09:24 <mnasiadka> ok then
13:09:42 <mnasiadka> after 2023.1 rmq pin fix merges - I think we should push for rc2 and final
13:10:03 <mnasiadka> and work out rmq and ansible mariadb/rmq rework in master and backport that to 2023.1 after final release
13:10:14 <mnasiadka> frickler, bbezak, mgoddard, kevko: what do you think?
13:10:48 <frickler> +1
13:11:37 <mnasiadka> ok then, everyone else is asleep I guess
13:11:52 <mnasiadka> when https://review.opendev.org/c/openstack/kolla/+/884815 merges - I'll post rc2 and then final
13:11:53 <mmalchuk> +1 too
13:12:17 <mnasiadka> #topic Current cycle planning
13:12:28 <SvenKieske> I was not asked; but I hope the mariadb changes don't turn out to be too complex :)
13:12:55 <mnasiadka> SvenKieske: there's a patch raised by mgoddard https://review.opendev.org/c/openstack/kolla-ansible/+/884182
13:14:03 <mnasiadka> but we'd need first to make cephadm-upgrade jobs better in https://review.opendev.org/c/openstack/kolla-ansible/+/884488
13:14:05 <SvenKieske> yeah I know, I'm on the reviewer list :) so I hope that patch works out well, as I said, it's fairly complex/large to backport imho
13:14:50 <frickler> it shouldn't be much work to backport to 2023.1
13:15:01 <frickler> backporting further I would not support
13:15:11 <mnasiadka> yes, we just need to backport to 2023.1
13:15:48 <mnasiadka> ok, for current cycle - I'll clean up the whiteboard this week, add priorities for that cycle
13:15:59 <mnasiadka> obviously podman and let's encrypt are getting moved to Bobcat
13:16:09 <mnasiadka> hopefully we can find somebody interested in getting those in
13:16:38 <mnasiadka> #topic Additional agenda (from whiteboard)
13:16:54 <mnasiadka> (ihalomi): do we really need shared /run mount among containers?
13:17:00 <mnasiadka> ihalomi: didn't we discuss it already?
13:17:55 <mnasiadka> I think we did
13:18:06 <SvenKieske> I guess that topic just never got deleted from the whiteboard? but I can't honestly remember the outcome.
13:18:13 <mnasiadka> Yeah, I deleted it now
13:18:22 <ihalomi> yes we did but outcome was that we need to look more into it
13:18:37 <SvenKieske> I guess it was agreed to add the needed /run subdirs?
13:18:57 <mnasiadka> Did you try to test doing the mount like tripleo does? I think /run is not shared in tripleo deployments?
13:19:02 <mmalchuk> about the priorities: I'm blocked by https://review.opendev.org/c/openstack/kayobe/+/881679 to continue work on repos.yaml
13:19:09 <mmalchuk> need help
13:19:15 <ihalomi> yea I tried it but we need to create these subdirs before each start of container
13:19:36 <mnasiadka> mmalchuk: repos.yaml is in kolla, this is only to support repos.yaml in kayobe - what further work are we talking about? something in kayobe?
13:19:49 <ihalomi> so we would have to add checklist for it into service files and systemd then runs creation before each start so it wont fail
13:19:59 <frickler> ihalomi: could some tmpfiles config help?
13:20:12 <mnasiadka> ihalomi: or just create that dir in kolla_container module?
13:20:22 <mmalchuk> I use kayobe for deploy
13:21:14 <ihalomi> but if you create it in module it gets deleted after each reboot of host
13:21:34 <ihalomi> fricklers idea could solve it
13:21:35 <mmalchuk> can't switch to redhat repos until this solved. this means full redeploy
13:21:47 <ihalomi> i can look into it
13:22:17 <opendevreview> Merged openstack/kolla stable/2023.1: rabbitmq: pin to 3.11.16  https://review.opendev.org/c/openstack/kolla/+/884815
13:22:20 <mnasiadka> I think you have no other choice :)
13:22:29 <mnasiadka> yay, time to raise rc2
13:22:47 <mnasiadka> second topic from SvenKieske
13:22:49 <mnasiadka> fix for https://bugs.launchpad.net/kolla/+bug/2019557 seems to be incomplete, help in debugging would be appreciated
13:23:21 <mnasiadka> I think the best fix is to pin td-agent to 4.4.2 with older version of elasticsearch plugin
13:23:30 <mnasiadka> instead of doing that dance
13:23:42 <mmalchuk> +1
13:24:02 <SvenKieske> okay, will iterate on the patch
13:24:34 <mnasiadka> actually my bad that I didn't do that earlier
13:24:38 <mnasiadka> SvenKieske: thanks
13:24:49 <mnasiadka> #topic Open discussion
13:25:29 <mhiner> I want to ask about mariadb issue I have in migration patch
13:26:20 <mnasiadka> and the issue is?
13:26:24 <mhiner> On multinode setup, deployment fails when there is already existing mariadb volume saying I should run mariadb_recovery pb
13:26:53 <mhiner> Is there a way to bypass this or should I just run that playbook?
13:27:25 <mnasiadka> when you stop all mariadb containers - there is no other way than to run recovery playbook
13:27:38 <mnasiadka> well, maybe on single node we survive
13:27:48 <mnasiadka> but multinode - you would need to go host by host
13:28:03 <mhiner> yes, single nodes are allowed to continue
13:28:09 <mhiner> thanks for clarification
13:29:38 <mnasiadka> ok, anyone else?
13:31:34 <mnasiadka> I guess not
13:31:37 <mnasiadka> thanks for coming!
13:31:39 <mnasiadka> #endmeeting