13:02:23 #startmeeting kolla 13:02:23 Meeting started Wed May 10 13:02:23 2023 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:23 The meeting name has been set to 'kolla' 13:02:28 #topic rollcall 13:02:34 o/ 13:02:39 o/ 13:02:44 o/ 13:03:06 \o 13:03:34 o/ 13:03:36 Maksim Malchuk proposed openstack/kayobe master: Add custom user_data content configuration for Bifrost https://review.opendev.org/c/openstack/kayobe/+/879554 13:03:42 sorry, my laptop just crashed.. 13:04:51 #topic agenda 13:04:51 * CI status 13:04:51 * Release tasks 13:04:51 * Regular stable releases (first meeting in a month) 13:04:51 * Current cycle planning 13:04:53 * Additional agenda (from whiteboard) 13:04:53 * Open discussion 13:04:55 #topic CI Status 13:05:04 seems we're green now 13:05:11 after all those weird breakages 13:05:18 #topic Release tasks 13:05:28 Basically 1st of June is release deadline for cycle-trailing projects 13:05:29 Kayobe CI red 13:05:41 mmalchuk: so please update the whiteboard 13:05:42 fix: https://review.opendev.org/c/openstack/kayobe/+/882820 13:06:25 lets merge it and it will be green 13:06:31 So we need to start cutting corners - for the 1st June deadline 13:06:39 I had a look in the Ansible bump issue 13:07:03 Found the commit in ansible-core that broke us, will start thinking how to overcome it 13:07:09 it not ansible, it molecule 13:07:31 #link https://github.com/ansible/ansible/issues/79776 13:07:35 setup.cfg have ansible-compat >= 2.2.0 13:07:37 mmalchuk: I'm not speaking about your patch 13:07:53 ok. sorry 13:08:26 this is the patch in question mnasiadka talks about afaik: https://review.opendev.org/c/openstack/kolla-ansible/+/881018 13:09:02 mnasiadka: if I could speed up something/help somewhere, just ask :) 13:09:04 yup, updated it with a link to a bug that broke us ;-) 13:09:10 nice 13:10:16 There is one patch in Kolla that will need merging, but first Rocky needs to have centos-release-openstack-antelope - I raised a bug in Rocky bug tracker and it seems it's in progress 13:10:20 there's an upstream fix already merged it seems? https://github.com/ansible/ansible/pull/79804 13:10:30 SvenKieske: it's the fix that broke us :) 13:10:35 ouch :D 13:10:55 testing now with force_handlers: true/false if that's an easy fix 13:10:58 but probably not 13:11:33 ok 13:13:47 mnasiadka whiteboard updated 13:13:59 Would be nice to get some reviews on https://review.opendev.org/c/openstack/kolla/+/882343 - it seems the version check is broken now ;-) 13:14:59 and we need it for https://review.opendev.org/c/openstack/kolla/+/825786/27 13:15:32 I can review that. in general it would be nice if dependencies are tracked/mentioned somewhere in the commit message or the bugtracker 13:16:03 well, those patches are stacked one on another, you can see that in the gerrit ui 13:16:18 relation chain - top right 13:16:49 #topic Current cycle planning 13:16:59 I think we've done that in the release tasks (I mean the planning) 13:17:09 #topic Additional agenda (from whiteboard) 13:17:17 yeah, in this case it's there, but not always ;) related to that: WIPs are often initially not marked as WIP, but maybe I'm just to fast to review. 13:17:47 SvenKieske: well, some people mark WIP in commit message, some people mark it as a flag in Gerrit, some people do both, some people do none :) 13:18:01 (mattcrees): With this precheck now added, should we enable RabbitMQ HA queues by default in Antelope? Precheck: https://review.opendev.org/c/openstack/kolla-ansible/+/880274 13:18:03 mattcrees: around? 13:18:08 Yep 13:18:42 Basically as the topic says, if people are happy that the precheck is enough then IMO we should enable RabbitMQ HA queues by default 13:19:14 I think it would be good to change the default, I already squashed 5+ bugs from people running non-HA on multinode with known problems 13:19:37 yeah, that would be nice, was there already a change open for that? 13:19:45 There's also backports of the precheck ongoing 13:20:06 SvenKieske: I don't think so, I'll propose one now 13:20:30 I just merged the backports 13:20:30 nice, will review, you can ping me about it 13:20:57 Will do 13:21:03 #agreed to change the RMQ HA queues by default in Antelope 13:21:21 the backports already all have one +2 and are just missing workflow/verified, so I guess I can't do much there 13:21:23 There's a topic by ihalomi - but he's not around 13:21:39 so I'll leave it for next week 13:21:47 #topic Open discussion 13:21:54 Anyone, anything? 13:21:55 yeah regarding: https://review.opendev.org/c/openstack/kolla/+/825786 he asked for help but there are still unadressed comments, so. 13:22:04 Kayobe reviews 13:22:13 1. https://review.opendev.org/c/openstack/kayobe/+/882820 13:22:19 2. https://review.opendev.org/c/openstack/kayobe/+/881679 13:22:25 both CI 13:23:12 mgoddard ask to fix kayobe-seed-images-* jobs ^^^ it fixed 13:23:32 molecule broken recently 13:23:44 also fixed 13:24:05 I've sent that on a different communication channel to Kayobe cores inside StackHPC, let's see if that gets reviewed. 13:24:24 thanks 13:24:30 SvenKieske: I have a feeling we need to push it over so it gets merged 13:26:35 yeah, might be, the docs comments can be addressed by us, I think. the tests not passing is the bigger issue I guess. 13:27:28 I'll have a look, probably we need to mock the docker version in more places 13:27:42 or once for everything that is not pre3.0.0 13:28:04 appreciated, as I'm still not very familiar with this part of the code. 13:28:50 I started triaging the bugs, kolla and kayobe look fine, kolla-ansible is another 180 bugs to triage 13:29:14 but I should get there before the summit, and we could start having weekly bug reports on the ML 13:30:00 or bugs managed in a proper way 13:30:26 Ok, anything else? or should we call it a day? 13:30:34 yeah, bug reports on the ML might be nice, I like that when neutron et al do this 13:30:50 I have the next meeting already scheduled, so.. 13:31:05 Ok then, thanks for coming - see you next week :) 13:31:07 #endmeeting