Friday, 2026-10-30

*** elodilles_pto is now known as elodilles07:01
opendevreviewJoan Gilabert proposed openstack/releases master: Create watcher 14.1.3, 15.1.3, 16.0.3, 17.0.1  https://review.opendev.org/c/openstack/releases/+/101289208:13
opendevreviewJoan Gilabert proposed openstack/releases master: [watcher] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095608:13
opendevreviewMerged openstack/releases master: [ironic] Final release of stable/2025.1  https://review.opendev.org/c/openstack/releases/+/101279110:38
opendevreviewMerged openstack/releases master: tooz 9.2.0  https://review.opendev.org/c/openstack/releases/+/101014512:36
opendevreviewMerged openstack/releases master: Release virtualbmc 3.4.0  https://review.opendev.org/c/openstack/releases/+/101286812:36
opendevreviewJoan Gilabert proposed openstack/releases master: Create watcher 14.2.0, 15.1.3, 16.0.3, 17.0.1  https://review.opendev.org/c/openstack/releases/+/101289212:50
opendevreviewJoan Gilabert proposed openstack/releases master: [watcher] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095612:50
opendevreviewMerged openstack/releases master: Create watcher 14.2.0, 15.1.3, 16.0.3, 17.0.1  https://review.opendev.org/c/openstack/releases/+/101289213:38
opendevreviewBrian Rosmaita proposed openstack/releases master: [cinder] Final Epoxy release  https://review.opendev.org/c/openstack/releases/+/101273814:26
opendevreviewJeremy Stanley proposed openstack/releases master: keystonemiddleware: OSSA-2026-050 stable releases  https://review.opendev.org/c/openstack/releases/+/101304514:36
elodillesfyi, i'm planning to start merging the Epoxy transition patches today, where it is possible (more than ~half have PTL-Approved+1 and can be merged i think). i'll double check the hashes before merging, of course.14:45
opendevreviewMerged openstack/releases master: [cinder] Final Epoxy release  https://review.opendev.org/c/openstack/releases/+/101273814:47
elodillesand then run the script to abandon open patches on the closed stable/2025.1 branches + if i'll get there, then i'll start the branch deletion as well... (if i run out of time, then i'll do that on Monday. we'll see)14:48
fungielodilles: this batch is just the services essentially, not libs yet, right?14:48
opendevreviewBrian Rosmaita proposed openstack/releases master: [cinder] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095314:48
elodillesfungi: libs + services as well. everything, basically. why?14:49
fungioh, i didn't see one specifically for keystonemiddleware, but i just pushed a change to tag 2025.1 with a new security release14:49
elodillesfungi: this is the patch: https://review.opendev.org/c/openstack/releases/+/101095514:50
elodillesi saw your release and plan to review that ASAP o:)14:50
fungii wasn't originally going to include it in the advisory, but since the stable branch was still open yesterday i went ahead and covered it14:50
elodillesfungi: no problem14:51
elodilleswill wait for that to merge14:51
elodillesi just hope we haven't introduce any regression with these late releases on stable/2025.1 o:)14:52
elodilles(...as we won't have a 2nd chance to release if there is any regression... :X)14:52
fungiyeah, me too14:52
elodillesbut anyway, beyond official releases, folks can do downstream releases from unmaintained/2025.1 if they need...14:53
elodillesfungi: i've commented on the keystonemiddleware release patch, can you please take a look? https://review.opendev.org/c/openstack/releases/+/101304515:06
fungichecking15:06
fungielodilles: i'm good with switching to minor increases if keystone folks are15:09
elodillesfungi: ACK. i think it's a bit better to highlight a bit more the default value change to operators as this upgrade can have impact on them as far as i understand15:49
opendevreviewMerged openstack/releases master: [venus] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096816:19
elodillesrelease-team: we have a tag-release job failure, it's on an inactive project (venus). it seems that bot could not push 'create-2025.1' patches to it on the new unmaintained/2025.1 branch: https://zuul.opendev.org/t/openstack/build/97548728166443729749f5984e6b9fb7/log/job-output.txt#206616:36
elodillesi guess this is only an issue because of the inactivity, right? O.o16:37
fungii'll double-check16:37
elodilles(the 2025.1-eom tag and the unmaintained/2025.1 branching was successful, fwiw)16:38
fungivenus was retired 2026-06-0216:39
fungilooks like it did not get stable branches after 2025.2 but the stable/2025.1 to unmaintained/2025.1 migration shouldn't need them16:41
elodillesthe last release was done for 2025.2 Flamingo16:41
fungiyeah, so the repository in gerrit uses the openstack "retired" acl16:43
fungihttps://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/retired.config16:44
fungithat also inherits some permissions and settings from https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/meta-config.config16:45
fungi"You need 'Create Change' rights to upload code review requests." is the hint in the gerrit output16:46
elodilles+116:46
fungimaybe we should confirm with the tc to give the release managers group permissions in the retired acl, to allow closing down old branches?16:47
fungieither that, or we skip these tasks for retired repositories16:48
elodillesfungi: note that the tagging and branch creation was successful. the script / bot wanted to push the create-2025.1 patch to change 'defaultbranch=stable/2025.1' to 'defaultbranch=unmaintained/2025.1'.16:50
fungiyeah, which the acl doesn't currently allow for groups the release bot account is in16:50
elodillesand i wonder if folks want to push bug fixes to a retired but open project's stable branch (e.g. stable/2025.2 in this case) then it is possible or not. (should it be possible?)16:50
fungii think we should clarify with the tc, but probably they don't expect stable branches for retired projects to transition to unmaintained at all?16:51
fungii can get it on their meeting agenda for tuesday16:52
elodillesmaybe frickler remembers as he was always objecting to do this o:)16:52
elodillesfungi: ACK, thanks o/16:52
elodillesanyway, this time it was only venus project16:53
fungihttps://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html doesn't make reference to retired projects/deliverables, fwiw16:53
elodillesi think there is no other inactive project 16:53
fungiwell, venus isn't inactive, it's retired16:54
fungithe error was due to the specific acl which gets applied to retired projects16:54
elodillesoh, sorry, retired, yes o:)16:54
elodillesanyway, then i'm confident in continuing checking and approving the transition patches16:56
elodilleso:)16:56
fungiempirically speaking, the acl says that retired projects aren't expected to receive new changes on any branch, so creating unmaintained branches for them does seem pointless. maybe for clarity all remaining branches of a retired project should transition to eol at retirement, but that could get in the way of resurrecting a retired project too, which is why it would be good16:57
fungito get clear guidance from the tc on expectations16:57
elodilles+116:59
elodillesi do remember that in the past frickler suggested to move retired projects to EOL rather than moving to Unmaintained and we created EOL patches for them instead. but i forgot about that :( now the memories have started to come back... late.... :/17:01
elodillesalso, there are release-job-failures coming for x/networking-mlnx but i haven't checked the reason. note, that they are out of release team scope. jovial doing manual tagging as far as i understand, which triggers the jobs, but something is not setup correctly for them either :/17:11
opendevreviewMerged openstack/releases master: [adjutant] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096517:14
elodillesokay, tag-release job succeeded for this patch ^^^ and the patches are pushed by the script: https://review.opendev.org/q/topic:create-2025.1+branch:unmaintained/2025.117:23
elodillesso it's safe to continue17:23
opendevreviewJeremy Stanley proposed openstack/releases master: keystonemiddleware: OSSA-2026-050 stable releases  https://review.opendev.org/c/openstack/releases/+/101304517:32
opendevreviewMerged openstack/releases master: [blazar] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101097117:35
opendevreviewMerged openstack/releases master: [zun] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101092817:35
opendevreviewMerged openstack/releases master: [storlets] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101093517:37
opendevreviewMerged openstack/releases master: [tacker] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096917:39
fungielodilles: gtema okayed the update to 1013045 now17:41
elodillesfungi: ack, thanks, will process that as well o/17:41
opendevreviewMerged openstack/releases master: [zaqar] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101094117:43
opendevreviewMerged openstack/releases master: [skyline] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101093217:43
elodillesfungi: this is just a heads-up, that there was a job failure the day before yesterday, it's probably a temporary infra issue: https://review.opendev.org/c/openstack/releases/+/1010926/2#message-1c24a5a23cf0a1f2b019f64f063cfe575488dca017:46
opendevreviewMerged openstack/releases master: [heat] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101094717:47
opendevreviewMerged openstack/releases master: [cyborg] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101093117:47
fungielodilles: thanks, `fatal: failed to iterate over '/opt/git/opendev.org/openstack/octavia-lib/.git/objects/'` looks like the first hint of a problem there?17:50
fungiand on the other job, `warning: error reading directory '/opt/git/opendev.org/openstack/octavia-lib/.git/objects/4f/': Bad message`17:52
opendevreviewMerged openstack/releases master: [mistral] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101093017:52
opendevreviewMerged openstack/releases master: [cinder] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095317:53
elodillesi guess octavia-lib was not properly available under /opt/git/opendev.org, some syncing issue? O.o17:53
fungii wonder if we have a corrupt openstack/octavia-lib git repository on one of the zuul executors17:53
fungior in the prepopulated cache on our test node images17:54
elodillesi remember you found one some time ago, didn't you? :-o17:54
opendevreviewMerged openstack/releases master: [watcher] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095617:54
Clark[m]//opt/git is the cache17:55
opendevreviewMerged openstack/releases master: [ironic] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101093917:56
fungiClark[m]: good point, so that's not what would have been pushed from the executor's cache17:56
fungisounds more likely to be baked into the test node image then17:56
elodillesjust a note, that the clone succeded some time after, when the patch was rechecked17:57
elodillesso it was a temporary issue17:57
Clark[m]Ya it's probably specific to that image in that region. Last time this happened I think we booted a node manually there and confirmed the broken repo17:58
Clark[m]Then we deleted the image(s)17:58
fungiboth ran on ubuntu-noble-8GB in raxflex-sjc317:58
fungiso could be a corrupt upload to that one region, right17:58
Clark[m]I think we decided last time this was a cloud software but not something we did. Anyone know the folks building Openstack software? :P17:58
fungii've met an openstack developer once17:59
elodilles:D17:59
elodillesmaybe if we could get some logs we could open a bug to them o:)18:13
elodillesbut now i need to go AFK :S18:14
opendevreviewMerged openstack/releases master: [octavia] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101092618:15
opendevreviewMerged openstack/releases master: [nova] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101092418:15
opendevreviewMerged openstack/releases master: [designate] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095918:15
opendevreviewMerged openstack/releases master: [swift] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096118:15
opendevreviewJeremy Stanley proposed openstack/releases master: keystonemiddleware: OSSA-2026-050 stable releases  https://review.opendev.org/c/openstack/releases/+/101304518:18
opendevreviewMerged openstack/releases master: [oslo] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101092718:22
opendevreviewMerged openstack/releases master: [neutron] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101094418:22
opendevreviewMerged openstack/releases master: [Telemetry] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101094818:22

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