14:00:03 <hberaud> #startmeeting releaseteam
14:00:03 <opendevmeet> Meeting started Fri Sep 22 14:00:03 2023 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:03 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:03 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:08 <hberaud> Ping list: elodilles armstrong
14:00:13 <hberaud> See you at line 441 https://etherpad.opendev.org/p/bobcat-relmgt-tracking
14:00:25 <elodilles> o/
14:02:01 <opendevreview> Carlos Eduardo proposed openstack/releases master: Release manila-tempest-plugin for 2023.2 Bobcat  https://review.opendev.org/c/openstack/releases/+/895561
14:02:03 <hberaud> ok, let's go!
14:02:08 <hberaud> #topic Review task completion
14:02:13 <hberaud> 1) Process any standing RC1 deadline exceptions
14:02:19 <hberaud> everything is done \o/ => https://review.opendev.org/q/topic:bobcat-rc1-deadline+is:open
14:02:24 <elodilles> \o/
14:02:27 <hberaud> 2) oslo.db + castellan release issues (hberaud)
14:02:31 <hberaud> so
14:02:51 <hberaud> oslo.db seems almost fixed
14:03:02 <hberaud> https://review.opendev.org/c/openstack/requirements/+/896053
14:03:47 <hberaud> we just have a post job failure on keystone but I don't think this is related to the sqla migration
14:03:52 <frickler> someone needs to talk to masakari or propose a patch for them
14:04:16 <hberaud> frickler: you mean release patches?
14:04:21 <frickler> to add sqla-migrate to their requirements
14:04:36 <frickler> in order for 896053 to pass
14:04:51 <frickler> no, patch for masakari reqs.txt
14:04:53 <elodilles> hberaud: you mean s/keystone/masakari/ right?
14:05:12 <frickler> there was an unstable keystone failure, too, but that can be ignored
14:05:13 <hberaud> frickler: what if we relocate sqlamigrate on oslo.db's requirements?
14:05:32 <hberaud> instead of fight with masakari
14:06:20 <hberaud> moving sqla-migrate from test-req to reqs should solve the issue, isn't?
14:06:23 <frickler> that might also work, but will require yet another release
14:06:45 <ttx> o/
14:06:45 <hberaud> I think this patch would be more short
14:06:47 <ttx> sorry I'm late
14:06:53 <hberaud> s/patch/path
14:06:54 <frickler> 3rd option is to just make the job on reqs n-v
14:07:46 <frickler> stephenfin: ^^ want to share your opinion on this?
14:07:49 <hberaud> personally I prefer the oslo.db solution, hence we don't have surprise again with missing  reqs
14:09:26 <frickler> I guess you can propose a patch for that and then have the possible discussion continue there
14:09:32 <hberaud> concerning castellan I proposed a new release ~ 1h ago => https://review.opendev.org/c/openstack/releases/+/896237
14:09:35 <elodilles> if i understand correctly sqla-migrate is not a direct dependency of oslo.db, is it?
14:09:42 <hberaud> yeah, I'll submit the patch after the meeting
14:09:51 <frickler> elodilles: it was earlier, now it no longer is
14:10:17 <hberaud> elodilles: the problem come from this move https://opendev.org/openstack/oslo.db/commit/caebf7620e94999ee6cfb5bcfad1db50572008bf
14:10:41 <hberaud> we just have a to move this reqs back as it was before
14:10:57 <frickler> yes, and we did that patch because release automation was complaining
14:11:04 <stephenfin> hberaud: the problem came from masakari being an effectively dead project that isn't merging patches
14:11:13 <frickler> but we later resolved that that only affected a patch release
14:11:14 <hberaud> yeah too
14:11:14 <elodilles> hberaud: oh, so this is a new patch already on stable/2023.2
14:11:34 <hberaud> elodilles: yeah
14:11:53 <stephenfin> sqlalchemy-migrate is a direct dependency of masakari. They should include it in their requirements.txt
14:11:53 <hberaud> stephenfin: I totally agree with you
14:11:56 <ttx> tempted to revert that change yes
14:11:59 <elodilles> hberaud: then "it's too late", +1 for adding back to oslo.db
14:12:20 <elodilles> ttx: +1
14:12:44 <stephenfin> the addition of sqlalchemy-migrate was also a new patch on stable/2023.2
14:12:45 <ttx> but we can also push that patch in masakari, so that it's fixed (one day)
14:13:15 <frickler> stephenfin: well it was the revert of removing it, so not new compared to 2023.1, right?
14:13:36 <stephenfin> yes, true
14:13:45 <hberaud> https://review.opendev.org/c/openstack/oslo.db/+/896214
14:15:07 <hberaud> ttx, elodilles please have a look to the castellan patch
14:15:16 <hberaud> https://review.opendev.org/c/openstack/releases/+/896237
14:16:06 <frickler> hberaud: btw. thanks for https://lists.openstack.org/pipermail/openstack-discuss/2023-September/035183.html , I hope we can make something happen on the TC side
14:16:14 <hberaud> stephenfin: this patch is dedicated to C? https://review.opendev.org/c/openstack/requirements/+/879743
14:16:22 * elodilles looking
14:16:28 <stephenfin> yup, for C
14:16:30 <hberaud> frickler: np
14:17:19 <ttx> +2
14:17:52 <hberaud> and as said frickler on my side I opened a thread more dedicated to open a discussion on how to manage this kind of issue on the long terms https://lists.openstack.org/pipermail/openstack-discuss/2023-September/035183.html
14:18:20 <hberaud> ttx: thx
14:18:44 <elodilles> +2+W
14:18:44 <hberaud> and I think that's all for now concerning this topic
14:18:53 <fungi> the tc does have authority to request core reviewer permission to any openstack project and approve changes
14:19:12 <hberaud> then this is a good news
14:19:19 <fungi> though i think they should consider any need to exercise that a strong signal of abandonment
14:19:38 <hberaud> agree
14:19:40 <ttx> they should more actively retire inactive projects while we still can (start of cycle rather than end of cycle)
14:19:52 <elodilles> ttx: ++
14:19:57 <hberaud> ++
14:19:58 <ttx> but for now, masakari is in
14:21:06 <elodilles> somewhat related: now i looked at not merged upper constraints bumping patches: https://review.opendev.org/q/topic:new-release+branch:master+is:open
14:21:14 <elodilles> is there any critical among them? ^^^
14:21:31 <elodilles> similar like oslo.db / castellan were?
14:22:14 <frickler> there is oslo.messaging, but I'm unsure about the details
14:22:42 <frickler> https://review.opendev.org/c/openstack/requirements/+/892919
14:23:40 <hberaud> will check this oslo.messaging bump after the meeting
14:24:09 <elodilles> hberaud: thanks!
14:24:30 <fungi> as long as oslo.messaging 14.4.0 made it in, that fixes a security vulnerability
14:24:55 <frickler> fungi: that's exactly the issue, it is breaking some projects
14:25:16 <frickler> but the failure is not always covered by testing from what I've heard
14:25:46 <hberaud> yeah this security fix is known to break some services
14:25:54 <elodilles> :S
14:26:09 <fungi> yeah, i still haven't requested a cve for it because it's been unclear if anyone was going to make oslo.messaging less breaky or try to merge fixes to the services being broken by it
14:27:05 <fungi> granted, i was on the fence about whether we'd issue an advisory at all, it seems fairly low-risk but we don't have earlier precedent for treating notifications as sensitive data
14:27:42 <fungi> so i guess if we issue an advisory for it after 2023.2 that's probably not the end of the world
14:27:58 <hberaud> yeah
14:28:50 * fungi makes a note to add a comment on the bug saying this is the current hold-up
14:29:11 <hberaud> thanks I'd suggest to continue the discussion directly on the patch
14:29:19 <elodilles> ++
14:29:24 <fungi> yes, or in the bug report
14:29:31 <hberaud> yup
14:29:43 <hberaud> anything else concerning this topic?
14:30:04 <hberaud> ok next task
14:30:08 <hberaud> 3) Gracefully release tempest plugins with latest changes available (elod)
14:30:17 <hberaud> https://review.opendev.org/q/topic:bobcat-tp-latest
14:30:35 <elodilles> half of them have merged
14:30:50 <elodilles> we have some where we have -1s from team
14:31:28 <elodilles> and i've +2+PTL-Approved+1'd those where we can continue with merging if everything is OK
14:31:36 <frickler> and we've had a team wondering where their patch was ;)
14:31:37 <hberaud> ack
14:32:23 <hberaud> some gates seems broken
14:32:31 <elodilles> frickler: yepp, we only release IFF there were newly merged patches ;)
14:32:34 <hberaud> https://review.opendev.org/c/openstack/releases/+/895567
14:32:42 <hberaud> https://review.opendev.org/c/openstack/releases/+/895562
14:32:43 <elodilles> OR there's no release at all :X
14:33:11 <hberaud> https://review.opendev.org/c/openstack/releases/+/895563
14:33:33 <elodilles> hberaud: right, yes, there are those where gate is broken
14:33:43 <hberaud> but gmann said that he is ok to merge them
14:34:04 <elodilles> i guess we should release anyway and hope the best they fix their gates
14:34:05 <opendevreview> Merged openstack/releases master: Castellan 4.3.0  https://review.opendev.org/c/openstack/releases/+/896237
14:34:13 <hberaud> wfm
14:34:31 <ttx> +1
14:34:35 <frickler> at least some of these are on my list to discuss as questionable for the next cycle
14:34:42 <elodilles> we had this (unfortunately) in the past...
14:34:53 <elodilles> frickler: +1
14:35:51 <hberaud> I just approved those without replies
14:36:19 <hberaud> anything else concerning this task?
14:36:51 <hberaud> 4) On Monday, generate stable branches for all cycle deliverables that are still missing one (elod)
14:37:04 <hberaud> https://review.opendev.org/q/topic:bobcat-missing-stable-branches
14:37:12 <hberaud> https://review.opendev.org/c/openstack/releases/+/894778
14:37:31 <elodilles> yepp, we have those 2 ^^^ horizon + python-barbicanclient
14:37:49 <hberaud> I see the horizon patch is now ok
14:37:57 <elodilles> yepp
14:38:26 <elodilles> i was hesitant to update python-barbicanclient, as we are way over client-lib deadline, but maybe it's better to release
14:38:36 <elodilles> to have the gate fix in the final release
14:38:47 <elodilles> what do you think?
14:39:01 <ttx> yeah it's not a functional change
14:39:06 <hberaud> concerning barbican I agree with you, fix could be released through a RC2
14:39:31 <elodilles> ACK, then i'll update the patch ASAP
14:39:38 <hberaud> ok
14:39:47 <ttx> standing by for +2
14:39:54 <hberaud> +1
14:39:56 <ttx> release like it's Friday
14:40:07 <hberaud> :)
14:40:42 <hberaud> 5) After all the projects enabled in devstack by default have been branched, we can engage with the (elod)
14:40:52 <opendevreview> Elod Illes proposed openstack/releases master: [barbican] Create 2023.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/894778
14:41:06 <elodilles> there you go ^^^
14:41:11 <hberaud> yep
14:41:21 <elodilles> PATCH version bump should be OK i hope
14:41:58 <frickler> is horizon enabled by default in devstack? I need to check
14:42:00 <elodilles> s/i hope/i think/
14:42:16 <hberaud> lgtm
14:42:31 <ttx> +3
14:42:58 <hberaud> so, if I'm right, we still miss this one to engage with QA, etc...
14:43:07 <elodilles> if we release horizon, then it's not a question anymore :)
14:43:58 <opendevreview> Merged openstack/releases master: Release magnum-tempest-plugin for 2023.2 Bobcat  https://review.opendev.org/c/openstack/releases/+/895560
14:44:02 <opendevreview> Merged openstack/releases master: Release barbican-tempest-plugin for 2023.2 Bobcat  https://review.opendev.org/c/openstack/releases/+/895548
14:44:06 <elodilles> do we want to wait for PTL-Approved on horizon branch cut patch?
14:44:07 <frickler> it is indeed, so go, go, go, release ;)
14:44:11 <hberaud> horizon just need a second review
14:44:39 <elodilles> (well, the release is already happened, we just need the branch cut there)
14:45:01 <hberaud> I think we can go
14:45:23 * elodilles agrees
14:45:27 <opendevreview> Merged openstack/releases master: Release kuryr-tempest-plugin for 2023.2 Bobcat  https://review.opendev.org/c/openstack/releases/+/895559
14:45:29 <elodilles> i've +2+W'd
14:45:29 <opendevreview> Merged openstack/releases master: Release zun-tempest-plugin for 2023.2 Bobcat  https://review.opendev.org/c/openstack/releases/+/895575
14:45:32 <opendevreview> Merged openstack/releases master: Release freezer-tempest-plugin for 2023.2 Bobcat  https://review.opendev.org/c/openstack/releases/+/895556
14:45:34 <opendevreview> Merged openstack/releases master: Release octavia-tempest-plugin for 2023.2 Bobcat  https://review.opendev.org/c/openstack/releases/+/895566
14:45:36 <ttx> boo you beat me to it
14:45:51 <elodilles> :)
14:46:05 <elodilles> double-approved :)
14:46:24 <hberaud> elodilles: so I suppose you will engage discussion after the meeting?
14:46:49 <elodilles> yepp, i'll start the QA/I18N/Req task after the meeting
14:46:50 <elodilles> right
14:46:56 <hberaud> ack
14:46:59 <hberaud> thanks
14:47:05 <hberaud> then move on
14:47:14 <hberaud> 6) Ensure that all projects that are publishing release notes have the notes link included in their deliverable file (hberaud)
14:47:22 <hberaud> https://review.opendev.org/c/openstack/releases/+/896240
14:48:17 <hberaud> as always I think we will have PTL who will say that they are not listed there, I think we could add their links in a follow-up patch
14:48:28 <elodilles> note: we don't need to wait for PTLs to approve the patch ^^^ if it looks right (generated patch) we can merge it
14:48:37 <hberaud> wfm
14:48:41 <elodilles> hberaud: ++
14:48:50 <ttx> Yeah, how about we wait Monday to give them a chance to review it?
14:48:57 <opendevreview> Merged openstack/releases master: Release sahara-tests for 2023.2 Bobcat  https://review.opendev.org/c/openstack/releases/+/895567
14:48:58 <ttx> then we just +2 it
14:48:58 <hberaud> but I think we can wait early monday to catch issues
14:49:14 <hberaud> agree with thierry
14:49:49 <hberaud> this kind of update is quickly generated
14:50:23 <hberaud> 7) Let cycle-with-rc projects iterate on RCs as needed. The final release candidate for each project needs to be prepared at least one week before the final release date
14:50:59 <elodilles> this is more like a guideline ^^^
14:51:06 <elodilles> i haven't seen any rc2 yet
14:51:07 <hberaud> so I don't think we things to do there, I see that the nova team already proposed a RC2
14:51:21 <ttx> ack
14:51:22 <elodilles> oh :-o
14:51:31 <elodilles> did they? :-o
14:51:47 <elodilles> ACK, I'll review it
14:51:50 <hberaud> ah I surely confused with a RC1 update
14:52:08 <hberaud> I see sylvain pushed a PS2 somewhere
14:52:19 <hberaud> so ignore my comment
14:52:22 <elodilles> OK, so no rc2 yet :)
14:52:36 <hberaud> ok move on
14:52:45 <hberaud> #topic Assign next week tasks
14:53:06 <hberaud> everything isnnow assigned
14:53:24 <hberaud> thanks elodilles
14:53:35 <elodilles> \o/
14:53:42 <hberaud> and I see elodilles is our next chair, thanks
14:53:52 <elodilles> np :)
14:54:01 <hberaud> #topic Review countdown email
14:54:08 <hberaud> https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:55:17 <ttx> lgtm
14:55:32 <frickler> do you want to include an update on last weeks warning section?
14:55:34 <elodilles> LGTM, too
14:55:45 <opendevreview> Merged openstack/releases master: [horizon] Create stable/2023.2  https://review.opendev.org/c/openstack/releases/+/895577
14:56:02 <hberaud> frickler: which warning?
14:56:41 <frickler> the one that was added about oslo.db and things
14:57:48 <hberaud> this topic already have its own thread, not sure that will be really useful there
14:57:57 <hberaud> any opinion?
14:58:47 <ttx> yeah, probably good as its own thread
14:59:16 <elodilles> +1
14:59:22 <hberaud> ack
14:59:25 <ttx> need to jump to my next meeting
14:59:31 <hberaud> sent
14:59:44 <hberaud> #topic Open Discussion
14:59:50 <elodilles> ttx: o/
14:59:55 <hberaud> Anything else that you want to discuss today?
15:00:01 <elodilles> i don't have any topic
15:00:01 <ttx> nothing from me
15:00:07 <hberaud> ttx: np, thanks
15:00:41 <hberaud> We fulfiled our time slot :)
15:01:17 <hberaud> thanks everyone!
15:01:25 <elodilles> thanks hberaud o/
15:01:26 <hberaud> #endmeeting