Wednesday, 2024-02-28

opendevreviewTakashi Kajinami proposed openstack/releases master: Create new oslo.context release for 2024.1  https://review.opendev.org/c/openstack/releases/+/91045001:35
opendevreviewTakashi Kajinami proposed openstack/releases master: Retire puppet-sahara: Mark the deliverables as retired  https://review.opendev.org/c/openstack/releases/+/91045602:04
opendevreviewTakashi Kajinami proposed openstack/releases master: Retire puppet-sahara: Mark the deliverables as retired  https://review.opendev.org/c/openstack/releases/+/91045604:30
tonybtkajinam, damani, elodilles_pto, frickler:  Not sure how to proceed with: https://review.opendev.org/c/openstack/requirements/+/910221/comments/98ad1045_768609eb04:32
opendevreviewTim Burke proposed openstack/releases master: Release final python-swiftclient for 2024.1 Caracal  https://review.opendev.org/c/openstack/releases/+/91021004:36
fricklertonyb: we did need to do some wild last minute changes for the last release in order to be able to release something working, I guess this is still fallout from that situation?05:56
fricklergmann: elodilles_pto: oh my, we really missed one patch. I guess that's mostly my fault because the topic was changed when I rebased it, but then later I only checked for open reviews with the default topic https://review.opendev.org/c/openstack/releases/+/906565 will approve that one now05:57
gmannfrickler: thanks.06:02
fricklerhmm, seems I need to actually delete that W-106:17
tonybfrickler: I guess so.06:20
tonybI don't know the best way to get make forward progress from where we're at.06:20
opendevreviewMerged openstack/releases master: [Quality Assurance] Transition Yoga to Unmaintained  https://review.opendev.org/c/openstack/releases/+/90656506:31
tkajinamtonyb, frickler I've already submitted the patches to nova and glance to unblock the test failures and IMO we can merge that bump once these patches land.07:03
tkajinamquickly searching projects dependent on castellan I'm aware that tacker may be affected by that change so I'll take care of it... sahara may be also affected but I'm unsure if it can be fixed now, since the project is badly unmaintained07:04
tkajinamhmm ok tacker is not using KeyManager from castellan actually so it should be fine07:06
tkajinamsahara is not using it either, so is not be affected07:07
fricklertkajinam: thanks for the update, I'll keep an eye on those fixes07:08
tonybtkajinam: Thanks.07:10
tonybtkajinam: Can you link to the nova/glance patches ?07:10
tonybtkajinam: or ... add Depends-On metadata to the upper-constraints change07:12
tkajinamyes. give me a min07:12
tonybtkajinam: Thanks :)07:12
tkajinamI wonder why I missed these require bump problems at the last cycle. probably I was not online after I returned my laptop to my prev. company and didn't yet have a replacement at that timing...07:17
tkajinammy local testing passed but we can double-check outcome from the updated requirements patch. I've left messages in nova/glance channels to request reviews...07:20
tonybtkajinam: Thanks07:21
fricklerfungi: iiuc the task to generate a new release key is still pending? or did I miss this somewhere?07:52
damanihi11:41
fungifrickler: still pending, yes. i came down with the flu just as i was planning to start on it13:01
opendevreviewIan Y. Choi proposed openstack/releases master: Tag governance 0.16.0 for Feb 2024 elections  https://review.opendev.org/c/openstack/releases/+/91052315:16
opendevreviewIan Y. Choi proposed openstack/releases master: Add 2024.2/"D" Election timeline to the schedule  https://review.opendev.org/c/openstack/releases/+/90515415:25
clarkbI think I've just discovered a bug where gitea treats branches in git repos case insensitively and fails if we hae branches in a git repo that would collide because git itself is case sensitive18:07
clarkbI'm leaving a heads up here since the release team does a lot of branch management for openstack. Basically ensure that all branch names created are unique if treated insensitively18:07
clarkband I'll be filing a bug later today18:08
noonedeadpunkhey folks! any guyess what could be causing this? https://zuul.opendev.org/t/openstack/build/421d757dd6f6476381e530440442a68a/log/job-output.txt#70418:08
noonedeadpunkfeels ery related to removal of stable/yoga. But somehow can't reproduce locally...18:09
noonedeadpunkor well.. maybe I should try clonning the repo from scratch...18:09
noonedeadpunkyeah... weird, I don't have any local references of stable/yoga...18:11
noonedeadpunkmaybe some cache or smth...18:12
noonedeadpunkanyway - any idea how to fix that and not loose release notes for the release?:)18:12
clarkbnoonedeadpunk: git won't delete local branches by default18:14
noonedeadpunkyeah, I didn't have local branches, but somehow could checkout to origin/stable/yoga 18:14
noonedeadpunkwhile it's not present18:14
noonedeadpunknot sure why, but anyway. Was able to reproduce cloning from scratch.18:15
noonedeadpunkstill clueless about how to solve that....18:15
noonedeadpunkas reno fails when trying to build for stable/yoga18:15
noonedeadpunkwhile does not for stable/pike for instance18:16
clarkbbecause you had origin/stable/yoga from a git remote update or similar and git won't remove those by default iirc18:17
noonedeadpunk`git branch -d origin/stable/yoga` was saying `error: branch 'origin/stable/yoga' not found.` but checkout worked... but anyway - that's not the issue that bothers me anyway :)18:18
noonedeadpunkbut more - how to make reno work18:18
noonedeadpunkshould we switch that to `unmaintained/yoga`? https://opendev.org/openstack/openstack-ansible/raw/branch/master/releasenotes/source/yoga.rst18:20
noonedeadpunkBut then how really old ones do not complain?18:20
noonedeadpunkLike https://opendev.org/openstack/openstack-ansible/raw/branch/master/releasenotes/source/pike.rst18:21
noonedeadpunkand like... changing to unmaintained/yoga is kinda weird, as release notes were related to times, when it was maintained... not saying it requires backporting to all stable branches18:24
noonedeadpunkaha, so it  can be switched to yoga-eom....18:26
noonedeadpunkand there's a bot patch, mhm https://review.opendev.org/c/openstack/openstack-ansible/+/90849918:27
noonedeadpunkbut it still needs to be backported I assume18:28
noonedeadpunkAnd still does not explain how this works for really old things...18:28
fricklernoonedeadpunk: we discusses that some weeks ago and the preference was to keep generating renos for yoga the same way we did for em branches18:52
fricklerand the change was only needed for master somehow. I'll have to look at the failure in your job in more detail18:53
fricklerI think that this may be a bug in the reno tool, someone will have to do more debugging19:02
noonedeadpunkyeah. having same flow as for EOL releases would make sense to me as well19:35
noonedeadpunkAnd I don;t see how yoga here is special...19:35
noonedeadpunkor well... there're 2 releases for Yoga...19:41
noonedeadpunk* 2 branches19:42
noonedeadpunkso it fails here https://opendev.org/openstack/reno/src/branch/master/reno/scanner.py#L550-L58819:43
noonedeadpunkmhm, I see now19:44
opendevreviewDmitriy Rabotyagov proposed openstack/reno master: Respect EOM tag for branches in unmaintained status  https://review.opendev.org/c/openstack/reno/+/91054719:54
noonedeadpunkthis should fix it ^19:54
opendevreviewDmitriy Rabotyagov proposed openstack/reno master: Respect EOM tag for branches in unmaintained status  https://review.opendev.org/c/openstack/reno/+/91054720:04
*** Guest500 is now known as diablo_rojo_phone23:26

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