Friday, 2026-05-22

opendevreviewMerged openstack/releases master: Update 2024.last tempest releasenotes page link  https://review.opendev.org/c/openstack/releases/+/98920510:49
opendevreviewMerged openstack/releases master: Puppet OpenStack 2026.1 release  https://review.opendev.org/c/openstack/releases/+/98899511:59
opendevreviewElod Illes proposed openstack/releases master: [OSA] Cut stable/2026.1 branch for roles  https://review.opendev.org/c/openstack/releases/+/98966212:04
opendevreviewElod Illes proposed openstack/releases master: [OSA] Cut stable/2026.1 branch and release RC1  https://review.opendev.org/c/openstack/releases/+/98968712:08
opendevreviewElod Illes proposed openstack/releases master: [kolla] Cut stable/2026.1 branch and release RC1 for Kayobe  https://review.opendev.org/c/openstack/releases/+/98972212:11
elodillesrelease-team: it seems we have a bunch of release-openstack-puppet release job POST_FAILURE now :/ for example: https://zuul.opendev.org/t/openstack/build/757b046f13f74aad97d507a5b9f9303912:22
elodillesit seems there is an auth issue towards Puppet Forge :S12:23
opendevreviewMerged openstack/releases master: Release glance_store for Hibiscus-1 milestone  https://review.opendev.org/c/openstack/releases/+/98913112:31
elodillesreminder: weekly meeting in less than 30 mins13:33
elodilles#startmeeting releaseteam14:00
opendevmeetMeeting started Fri May 22 14:00:28 2026 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'releaseteam'14:00
elodillesPing list: release-team14:00
elodilles#link https://etherpad.opendev.org/p/hibiscus-relmgt-tracking14:00
ttxo/14:00
elodilleswe are @ line 10014:01
elodilleso/14:01
fungiohai14:01
elodilleshey o/14:02
elodillesokay, let's start \o/14:02
elodilles#topic Review task completion14:02
elodilles- Review any remaining milestone-1 exceptions. (all)14:02
elodilles#link https://review.opendev.org/q/topic:hibiscus-milestone-1+is:open14:02
elodillesthe list is empty14:03
ttx\o/14:03
elodilles~o~14:03
elodilles- Ensure that all new-release patches in requirements repository for the milestone-1 releases are merged. (all)14:03
elodilles#link https://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release14:03
elodillesyepp, one patch is on the gate currently14:04
elodillesand the glance_store patch was created recently14:04
elodillesbut all the others have merged14:05
elodillesso we are on track14:05
elodilles- from week R-20: Ensure that all trailing projects have been branched for the previous series. (elod)14:05
elodillesso the summary here:14:05
elodilles    Kolla have branched earlier14:05
elodilles    Puppet OpenStack branched / did their final 2026.1 Gazpacho release this week14:05
elodilleswell, actually, i've +W'd the patch today14:06
elodillesbut it was released14:06
elodillesoh, btw, we had a release job issue there :/14:06
fungiyeah, i was wondering about that one. the related puppet-ceph release request has a validation issue14:06
elodillesfungi: note that it's not just puppet-ceph, but all the other puppet-* deliverables :S14:07
elodillesi just copied puppet-ceph as example :/14:07
fungiah14:07
elodillesso basically i think all the post-release jobs needs to be re-enqueued if possible, after the Puppet Forge authentication issue is solved :/14:07
elodillesis that possible? what do you think?14:08
fungi"Forge API auth failed with code: 400"14:08
elodillesyepp, that's the error14:08
fungii wonder if they need to update their credentials, i'll have to track down what/where those come from14:08
fungiwill take a look into that right after the meeting14:09
elodillesit looks like they need to update, yes :/14:09
elodillesfungi: thanks in advance o/14:09
elodillesso, let's continue the task assessment14:09
elodilles    OpenStack Ansible and Kayobe are still waiting to be branched14:09
elodilles    i've pushed patches for them:14:09
elodilles#link https://review.opendev.org/q/topic:gazpacho-cycle-trailing-stable-branch14:10
elodillesthough ~2 weeks ago both team confirmed they are working on the release14:10
elodillesanyway, the patches are there to not forget about it ^^^ they'll respond on the patches i'm sure14:11
fricklercc bbezak ^^14:11
elodillesthere's still 2 weeks time until the cycle-trailing release deadline14:11
elodillesbut the sooner the better14:11
elodillesthey should be in a code freeze period already14:12
elodillesand that were all about tasks14:12
elodilles#topic Assign R-17 week tasks14:13
bbezakFricker: thx14:13
elodillesnote that i'll be off at the end of week R-1714:13
elodillesso either we skip the meeting there,14:14
elodillesor someone else than me needs to chair it o:)14:14
ttxI can chair it I think14:14
elodillesthanks ttx \o/14:15
ttxyes that should work, let me add myself14:15
elodillesit is not a busy week, so the meeting shouldn't take long14:15
elodillescool. all taken then14:15
elodilleshmmm14:16
elodilles#topic Review weekly countdown email14:16
elodillesdo we have an email for today? :-o14:16
elodilleslet me check the process14:16
elodillesnope, there isn't any planned mail14:17
ttxnope14:17
elodillesso this is just an error in the agenda o:)14:17
elodillessorry :)14:17
elodilles#topic Open Discussion14:17
elodilles(fungi) Updating Our Launchpad Team14:17
elodilles#link https://launchpad.net/~openstack-release/+members14:17
elodilles    do we use it? included in a lot of driver teams, at least half the "active" members haven't been around for a decade14:18
fungiah, yeah i came across it earlier this week and wondered a few things14:18
fungii think historically we probably used it to update release milestones in deliverables?14:18
elodillesto tell you the truth i never used, and was not aware of it until last december, when frickler kindly added me o:)14:18
fungiit seems to be included in a lot of driver teams, so inherits a fair amount of privilege in openstack projects on lp14:19
fungifor example, it had nova private security bugs automatically shared with the people listed there, transitively, until very recently14:19
elodillesso the answer for the 1st question from me: i don't really use it14:20
fungiif we don't use it for anything now, i can work on getting it cleaned up/removed from random other projects' teams in lp14:20
elodillesand i don't know whether we'd cause any trouble if we'd clean up that list14:21
fricklerI'm not sure whether the LP integration to mark bugs resolved uses it?14:21
elodillesfrickler: but that would use some functional user acc or something like that, wouldn't it?14:22
fungii don't see any bot-owned accounts included in that team14:22
elodillesyepp, there isn't14:23
fungibug updates are managed with the hudson-openstack account, a.k.a. "OpenStack Infra" which is a member of the various bug teams like nova-bugs14:24
elodilleswhat i see is 'OpenStack Infra (hudson-openstack)' user which does the activities on bug reports14:24
elodilles++14:24
fricklerah, right, that has individual memberships https://launchpad.net/~hudson-openstack/+participation14:25
fricklerso cleanup should be fine for the release team14:26
ttxI'll have to drop soon, sorry. have a great weekend everyone14:26
elodillesso i guess if you want fungi then go on with the clean up and see if there will be any issue. i guess it's not a big deal to add back people if needed14:26
fungiwill do14:26
fungithanks ttx! you too!14:26
elodillesttx: same to you o/ thanks for coming!14:26
elodillesthanks fungi 14:27
elodilles#agreed fungi to clean up https://launchpad.net/~openstack-release/+members14:27
elodillesallright. anything else to discuss?14:27
fungii didn't have anything14:28
elodillesme neither14:28
fungii'll see what can be done about the puppetforge publication stuff and then try rerunning the jobs after it's resolved14:29
elodillesfungi: +114:29
elodillesokay, if nothing else to talk, then let's end the meeting!14:30
elodillesthanks everyone for participating o/14:30
elodilles#endmeeting14:30
opendevmeetMeeting ended Fri May 22 14:30:48 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:30
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-05-22-14.00.html14:30
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-05-22-14.00.txt14:30
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-05-22-14.00.log.html14:30
fungiaccording to https://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-puppet today is the first time those credentials have been exercised since october, so i guess they only release once per cycle these days14:31
fungihttps://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L17-L31 is where the job is defined14:33
fungihttps://opendev.org/openstack/project-config/src/branch/master/zuul.d/secrets.yaml#L635-L639 is the secret it's using, so yes it was never rotated after we reset all the zuul encryption keys in early january14:34
fungiokay, at one point in the past, the puppet ptl did hand over a login for that namespace account on puppetforge to the tact sig, so i'll see if i can reset it myself14:39
elodilles+114:41
fungihttps://review.opendev.org/c/openstack/project-config/+/989781 Reset PuppetForge password [NEW]15:21
fungionce that merges, i'll reenqueue openstack/puppet-aodh 28.0.0 in the release pipeline and see if it works15:22
fungirelease-openstack-puppet worked for that tag after updating the password and https://forge.puppet.com/modules/openstack/aodh/readme has the new version now, so i'll reenqueue the other 29 of them and keep an eye on the results15:52
elodillesyepp, it works \o/ https://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-puppet&skip=016:00
elodillesthanks fungi o/16:00
fungiokay, the remaining 29 previously failed releases are back in zuul now16:53
fungiand they've all completed successfully now, so we should be caught up from the earlier snag17:24
fricklercool, thx17:50

Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!