Thursday, 2022-01-20

*** mtreinish_ is now known as mtreinish05:13
*** diablo_rojo is now known as Guest113706:14
*** amoralej|off is now known as amoralej08:16
opendevreviewMerged openstack/releases master: New bugfix release of oslo.utils for yoga.  https://review.opendev.org/c/openstack/releases/+/82529709:08
opendevreviewMerged openstack/releases master: Release ovsdbapp 1.15.0  https://review.opendev.org/c/openstack/releases/+/82497509:33
elodilleshmmm, we have a release job failure again for the oslo.utils release: the publish-tox-docs-releases job failed09:49
elodilleshttps://zuul.opendev.org/t/openstack/build/c5f6ddc72117414aa7911b408fdecaf2/log/job-output.txt#982-98609:49
elodilles "found character '\t' that cannot start any token"09:49
elodillesif i remember correctly we had such issue in the past, and it was said to be intermittent issue, not an actual failure... but i'll check the yaml now...09:51
elodillesand i don't see \t in deliverables/yoga/oslo.utils.yaml09:54
elodillesis it worth to re-run the job or did we say before that docs jobs are not that relevant?09:57
*** priteau_ is now known as priteau11:16
ttxit's ok, the change will be picked up next time the job runs12:59
*** amoralej is now known as amoralej|lunch13:04
hberaudif only the docs job failed then I'd suggest to ignore it13:30
elodillesack13:35
*** amoralej|lunch is now known as amoralej14:00
*** diablo_rojo__ is now known as diablo_rojo14:52
opendevreviewAlex Schultz proposed openstack/releases master: Create ansible-role-chrony release  https://review.opendev.org/c/openstack/releases/+/82532314:55
elodillesfyi, i'm planning now to generate release patches for victoria, to ease the release-hurry before victoria-em in april (like i did with ussuri in august - e.g. https://review.opendev.org/c/openstack/releases/+/802059 )15:16
elodillesi don't know how much unreleased content there are, but i guess we will have many patches.15:17
hberaudack15:31
opendevreviewGoutham Pacha Ravi proposed openstack/releases master: Release python-manilaclient 3.2.0  https://review.opendev.org/c/openstack/releases/+/82553815:53
elodilleshberaud ttx : can you please review this patch? https://review.opendev.org/c/openstack/releases/+/822506 I completely forgot about this one.16:01
*** marios is now known as marios|out16:03
elodillesafter this i think we can EOL requirements' stable/ocata branch and finally move that branch to EOL16:03
opendevreviewMerged openstack/releases master: [OpenStackAnsible] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/82250616:15
noonedeadpunkfolks, smth weird happened with ^16:31
noonedeadpunkNow I see stable/ocata for already eol-ed repos16:32
noonedeadpunkah, might be you just didn't ran branch removal16:33
noonedeadpunkBut ocata-eol tag was created nicely!16:33
noonedeadpunkthe problem is that this triggered branch creation patcheshttps://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/825593 16:34
noonedeadpunk*patches https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82559316:34
noonedeadpunkI'm a bit afraid if tag wasn't re-created...16:35
elodillesnoonedeadpunk: yikes.... 16:51
elodillesas i see at least openstack-ansible's stable/ocata get tagged with ocata-eol16:52
elodillesthe problem is that ocata-eol was not created for all the repos at the sime time16:52
elodillesi'll abandon the create-eol patches :S16:53
elodillesi wonder whether we could have created a 2nd ocata-eol but now with openstack-ansible repo in it....16:55
elodillesand if i'm not mistaken we need to delete then a lot of stable/ocata branches now from openstack-ansible-* repos :S16:59
elodillesi need to run the cleanup script i guess :S16:59
elodillesyepp, the branches were re-created based on the 15.0.0rc1 hash 17:02
opendevreviewIury Gregory Melo Ferreira proposed openstack/releases master: Release multiple ironic deliverables for Ussuri  https://review.opendev.org/c/openstack/releases/+/82566218:23
*** amoralej is now known as amoralej|off18:35
iurygregoryelodilles, hey o/ I pushed https://review.opendev.org/c/openstack/releases/+/825662 to have a final release tagged before moving to EM, but it complains "deliverable <X> has status 'extended maintenance' for ussuri and cannot have new releases tagged" https://paste.opendev.org/show/812266/ any ideas on how to fix?18:56
elodillesiurygregory: oh, ok, yes, the ussuri-em state patch was merged, it seems that it does not allow further releases then.19:01
elodillesthere are some options what we can do, but let me discuss it tomorrow with the team19:02
elodilles(easiest is to revert the 'ussuri-em state' patch)19:03
elodillesbut we will see19:03
iurygregoryelodilles, no worries! tks!19:23
*** diablo_rojo is now known as Guest118919:29
elodillesnoonedeadpunk: the ocata branches have been removed (see the list: https://paste.opendev.org/show/812270/ ) so now we should be OK20:13
clarkbHey we found and fixed a couple bugs since yesterday's restart and will be doing another restart shortly. Everything should happen mostly gracefully except executors will likely be restarted non gracefully. When that happens any jobs that were running can be restarted.22:06
clarkbrelease queues appear empty and those jobs tend to be the only ones that are not so idempotent. If you can avoid releast activity for the next bit that would be great22:07

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