Tuesday, 2024-11-12

opendevreviewDaniel Bengtsson proposed openstack/releases master: Oslo dates for Epoxy schedule.  https://review.opendev.org/c/openstack/releases/+/93464207:41
elodillesrelease-team: i think we can slowly start the transition of projects' stable/2023.1 to Unmaintained. do i remember well that we have to start with 'requirements' and 'devstack'?08:28
elodillesand one more question: should we wait for final releases as some projects signalled that they want one more release before the transition08:30
elodillesif we don't wait then it means that the final release needs to be bumped in unmaintained/2023.1 of requirements08:30
elodillesso it might be a bit confusing :S08:31
elodillesopinions?08:31
fricklergood questions, I'd leave the answers up to the unmaintained liaisons to decide. but I have another question: how do we handle "By default, only the latest eligible Unmaintained branch is kept."?09:59
fricklerhmm. "The TC will maintain and document the full steps and guidelines ... for the eventual branch deletion." so maybe rather a TC topic10:02
elodillesfrickler: by default. but if there are volunteers to opt-in, then a branch can be kept longer.10:07
elodillesfrickler: and i'll volunteer to continue to keep open victoria if possible10:08
elodillesbobcat on the other hand will move directly to EOL next cycle. but that is another thing.10:15
elodillesfrickler: but back to the 1st question: it's somewhat release issue, whether we want to wait for all the final stable antelope release to happen before we start the machinery10:19
elodillesthough if we are not concerned about some version bump in upper-constraints.txt happen after requirements branch had moved to unmaintained/2023.1 then we can start the transition10:21
elodillesit's much nicer if we do the bumpings in requirements/stable/2023.1 but... meh... then we have to wait for all the final 2023.1 releases...10:22
fricklerelodilles: do you volunteer for all projects including like kolla, puppet and osa? also then the next question is to verify "The CI for all branches must be in good standing at the time of opt-in."10:22
elodillesfrickler: well, probably not for all projects, e.g. deployments projects can move to EOL10:23
fricklerelodilles: so we do need some more detailed process for that10:25
elodilles+110:25
opendevreviewRiccardo Pittau proposed openstack/releases master: Release python-ironicclient for Epoxy-1 milestone  https://review.opendev.org/c/openstack/releases/+/93463610:35
fricklerregarding the other question, I don't care about things happening in unmaintained branches, so unless you or some other unmaintainer asks us to wait, I'd say let's move on, we are behind in the schedule anyway10:36
elodillesbut it's not yet unmaintained, that's the point o:)10:39
elodillesand yes, we are behind the schedule :X10:40
fricklerwell as soon as we approve https://review.opendev.org/c/openstack/releases/+/934500 , requirements for 2023.1 will be unmaintained. and as you already voted +2 there, why should I not approve this now?10:46
elodillesi'm both OK to continue with the transition OR to wait until last signalled 2023.1 releases are out. o:)11:26
opendevreviewRodolfo Alonso proposed openstack/releases master: [neutron] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93448012:33
opendevreviewMerged openstack/releases master: [requirements] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93450013:46
opendevreviewMerged openstack/releases master: [Quality Assurance] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93448213:46
*** haleyb|out is now known as haleyb13:53
elodillesthanks frickler . as far as i see things are working / looks correct. so we can start slowly merging the rest of the PTL-Approved transition patches14:21
frickleryes, I'll look at those after my meetings14:23
elodillesthanks in advance o/14:30
opendevreviewMerged openstack/releases master: Release python-ironicclient for Epoxy-1 milestone  https://review.opendev.org/c/openstack/releases/+/93463615:35
opendevreviewMerged openstack/releases master: [magnum] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93448616:30
elodilles~o~16:30
elodillesthanks! let's get them merged \o/16:31
opendevreviewMerged openstack/releases master: [watcher] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93449216:41
opendevreviewMerged openstack/releases master: [manila] Release 18.2.1 from stable/2024.1  https://review.opendev.org/c/openstack/releases/+/93469116:50
opendevreviewMerged openstack/releases master: [manila] Release 17.3.1 from stable/2023.2  https://review.opendev.org/c/openstack/releases/+/93469216:50
opendevreviewMerged openstack/releases master: [trove] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93447816:50
opendevreviewMerged openstack/releases master: [octavia] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93446416:50
opendevreviewMerged openstack/releases master: [cyborg] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93447116:50
opendevreviewMerged openstack/releases master: [adjutant] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93450316:51
opendevreviewMerged openstack/releases master: [storlets] Transition 2023.1 Antelope to Unmaintained  https://review.opendev.org/c/openstack/releases/+/93447417:02
fricklermeh, lots of release failures due to broken log uploads, discussing in #opendev17:48
elodillesah, now i see them :/18:40
elodillesmost of them are POST_FAILURES :/ 18:41
elodilles(i've seen POST_FAILURES even on check-release-approval jobs today... :S without logs... afaiu, these failures are zuul errors, not related to the jobs at all, right?)18:43
clarkbwe removed teh swift regions that we believe were problematic and jobs starting after that poin should be happier18:43
clarkbelodilles: it depends on your perspective18:44
elodillesclarkb: ACK, thanks for the info18:44
clarkbthe errors occur in the jobs as they upload logs due to what we think is a sad keystone in rackspace18:44
clarkbzuul itself is running fine and executing the code as instructed but resources that the zuul jobs rely on are failing us18:44
elodillesah, i see. well, i meant something like this, not exactly 'zuul' to be honest o:)18:45
elodillesas i see, only a couple of publish-openstack-releasenotes-python3 job failed ( https://lists.openstack.org/archives/list/release-job-failures@lists.openstack.org/ ), i guess those are not that important to re-run as renos will be refreshed automatically at some point18:48
elodilles(these were just 2023.1-eom tagging patches, nothing new, important release notes should have been added)18:50
elodilless/new, important/new or important/18:50
fricklerat least one u-c proposal failed, I'll look into that tomorrow18:52
fricklerhttps://zuul.opendev.org/t/openstack/build/3273ba4fdcc24e87915ea288ca2ed0e118:52
elodillesfrickler: ACK, thanks for that18:55
elodillesbtw, i'll run now the abandon_patches_on_branch.sh script18:58
elodillesto avoid accidental merges on stable/2023.1 before they are deleted18:59
fricklerelodilles: just take care to keep devstack + reqs19:03
elodillesfrickler: now i ran only the patch abandoning script. (done)19:07
elodillesfrickler: i will run the branch delete script tomorrow when a couple of more projects transition19:09
elodilles(as I'm leaving for the day o:))19:09

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