14:00:33 <bbezak> #startmeeting kolla
14:00:33 <opendevmeet> Meeting started Wed Jan 24 14:00:33 2024 UTC and is due to finish in 60 minutes.  The chair is bbezak. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:33 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:33 <opendevmeet> The meeting name has been set to 'kolla'
14:00:39 <bbezak> #topic rollcall
14:00:42 <SvenKieske> o/
14:00:46 <frickler> \o
14:00:46 <kevko> \o/
14:01:01 <mattcrees> o/
14:02:30 <bbezak> #topic agenda
14:02:31 <bbezak> * Roll-call
14:02:31 <bbezak> * Agenda
14:02:31 <bbezak> * Announcements
14:02:31 <bbezak> * Review action items from the last meeting
14:02:31 <bbezak> * CI status
14:02:33 <bbezak> * Release tasks
14:02:33 <bbezak> * Regular stable releases (first meeting in a month)
14:02:35 <bbezak> * Current cycle planning
14:02:35 <bbezak> * Additional agenda (from whiteboard)
14:02:37 <bbezak> * Open discussion
14:02:59 <bbezak> #topic CI status
14:03:18 <bbezak> I think looks good after yesterday fixes by kevko and frickler
14:03:39 <bbezak> (I've been on sick leave for couple of days)
14:03:49 <kevko> podman cross-dependency missing
14:03:55 <SvenKieske> (me too ftr)
14:04:16 <bbezak> thx SvenKieske - sorry I was not around
14:04:28 <mmalchuk> o/
14:04:31 <SvenKieske> ah no problem, health comes first :)
14:04:59 <bbezak> kevko: yeah I wanted first to merge the 2023.2 k-a fix and then retest upgrades in your patch
14:05:12 <bbezak> if everything is sorted as it should
14:05:27 <kevko> bbezak: we have the same thoughts
14:05:38 <kevko> +1
14:05:40 <bbezak> nice
14:05:56 <bbezak> there was red status in kolla whiteboard, I've changed it to green, as it is If I'm not mistaken
14:06:00 <kevko> I hypnotize zuul status with a look
14:06:04 <bbezak> :)
14:06:36 <bbezak> #topic Release tasks
14:06:54 <bbezak> we were lacking several patches for release tasks unfortunately
14:07:01 <bbezak> I've raised them today
14:07:25 <bbezak> kevko has some automation/tooling ideas
14:07:33 <bbezak> patches are welcome
14:08:05 <kevko> i will propose some maybe ...if I will have some time :)
14:08:26 <bbezak> ok, thx
14:08:47 <bbezak> I've raised monthly stable release last week
14:08:58 <kevko> as you surely know, I have never done a release, I was completely surprised that there is no automated procedure for this
14:09:06 <bbezak> https://review.opendev.org/c/openstack/releases/+/906046
14:09:40 <bbezak> the process is pretty well documented, however it surely need an update - https://docs.openstack.org/kolla/latest/contributor/release-management.html
14:11:35 <bbezak> will add a note to myself to update this doc
14:11:40 <kevko> +1
14:12:04 <bbezak> #topic Current cycle planning
14:12:36 <bbezak> https://etherpad.opendev.org/p/KollaWhiteBoard#L209
14:12:54 <bbezak> any updates/questions on those priorities?
14:13:53 <bbezak> I don't have any update myself this week
14:13:58 <SvenKieske> not from my part at least, partly due to being sick the last two days :)
14:13:59 <bbezak> as far as my tasks
14:15:09 <SvenKieske> *technically three days
14:16:18 <bbezak> we've been mostly fire fighting CI since last week I can see. Let's hope next week will be more fruitful
14:17:00 <bbezak> #topic Additional agenda (from whiteboard)
14:17:18 <bbezak> I can see Container engine migration from mhiner
14:17:27 <bbezak> however I recall it was covered last week
14:18:11 <SvenKieske> I don't remember if this question was answered? > current CI tests don't gather container logs after migrating, any hints how to fix?
14:18:13 <bbezak> oh I remember that I didn't want to remove it from whiteboard as it has some valuable info
14:19:08 <kevko> SvenKieske: i think it is ..
14:19:19 <SvenKieske> in general I think it would make sense to update the whiteboard if questions are brought up and answered, no? not sure about the current approach here.
14:19:58 <frickler> I think I still need to look at those tests
14:20:20 <SvenKieske> at least - if I'm not misinterpreting - I don't see any answers to any of the questions there, like which cases we want to test. these answers are also missing from the patchset afaik.
14:21:23 <bbezak> yeah, it got valuable info/question - which is not yet fully answered, we can leave it here to track every week. if that makes sense
14:22:12 <SvenKieske> imho it only makes sense if it either contains the actual status of info/question, or a link to the status, or at the very list a link to the person working on answering the questions/providing the needed information
14:22:42 <bbezak> it probably should be discussed in the change itself
14:23:29 <SvenKieske> I'm fine with any solution, but I think only having the question there with no update serves little benefit. afaik the CI question is already in the review, but no answers :)
14:25:16 <bbezak> ok, let's continue discussion on that in the change. I'll double check if this info is in the change and then will remove from additional agenda part for now
14:25:26 <SvenKieske> ok
14:25:49 <bbezak> #topic Open discussion
14:27:14 <bbezak> Anything to discuss today? some changes to review?
14:27:28 <kevko> well, I wanted to review horizon patches :P
14:27:35 <kevko> and DNS
14:28:02 <mmalchuk> https://review.opendev.org/c/openstack/kolla-ansible/+/904400
14:28:04 <kevko> I am sure that after CI patches will be merged ..it will pass ..so if anyone have a time
14:28:11 <mmalchuk> please merge last fix to Yoga
14:28:31 <mmalchuk> and this: https://review.opendev.org/c/openstack/kolla-ansible/+/902382
14:28:42 <mmalchuk> should be abandoned since not needed
14:29:11 <mmalchuk> https://review.opendev.org/c/openstack/tenks/+/904333
14:29:28 <mmalchuk> not K/K-A but please review too
14:29:38 <mattcrees> I'm looking for second core reviews on two bugfixes, if anyone has the time: https://review.opendev.org/c/openstack/kolla-ansible/+/905500 https://review.opendev.org/c/openstack/kolla-ansible/+/905851
14:31:31 <frickler> added to my list
14:32:24 <bbezak> speaking of tenks, I've just notice it is failing in kayobe and k-a ironic jobs in master
14:32:31 <bbezak> "msg": "exceeded retry limit of 15 whilst waiting for resources to become available"
14:32:59 <bbezak> we need to look into that
14:33:36 <bbezak> I'll add info to whiteboard
14:33:40 <mmalchuk> have a link to failed job?
14:34:17 <bbezak> https://zuul.opendev.org/t/openstack/build/ea7e2d6d8f0d471e849e66cee46d3422
14:34:49 <bbezak> and in k-a https://zuul.opendev.org/t/openstack/build/935effc2148b436287d1ab1a057c7d7f
14:35:01 <bbezak> looks pretty fresh case
14:36:02 <mmalchuk> interesting
14:36:11 <mmalchuk> some regression in ironicclient?
14:36:23 <mmalchuk> oh... placementclinet
14:37:01 <bbezak> not sure, I literally just seen it in my patch for kayobe
14:37:17 <mmalchuk> strange... 4.2.0 released in Aug 2023
14:37:30 <SvenKieske> don't know if related but I proposed a fix for networking-baremetal, which I think is used in ironic, with regards to quorum queues: https://review.opendev.org/c/openstack/networking-baremetal/+/903995
14:38:00 <SvenKieske> didn't look into your issue though, so maybe totally unrelated.
14:38:42 <mmalchuk> imho not related since not used even if exists in container
14:38:59 <bbezak> interesting, let's see. I'll try to look into that tenks case probably tomorrow
14:38:59 <mmalchuk> it used when segments activated
14:39:48 <kevko> btw, i am too lazy to study code ..but from where is tenks installed in ci ?
14:39:51 <mmalchuk> have a look too
14:39:55 <kevko> tenks.yml
14:40:01 <kevko> where i can find it ?
14:40:59 <mmalchuk> deploy-tenks.sh
14:41:06 <kevko> hh, i know
14:41:07 <mmalchuk> tests/deploy-tenks.sh
14:41:18 <kevko> and there is tenks.yml
14:41:20 <mmalchuk> function deploy_tenks_logged
14:41:23 <mmalchuk> line #10
14:41:40 <mmalchuk> installed from source
14:42:22 <kevko> thanks
14:42:40 <bbezak> nice, so more firefighting, as usual
14:43:00 <bbezak> anything more to discuss?
14:44:18 <bbezak> ok, I guess no. thank you everybody!
14:44:21 <bbezak> #endmeeting