Monday, 2023-09-18

stephenfinfrickler: elodilles_pto: hberaud: Sorry, wasn't checking IRC Friday. Rather than reverting the many patches, could we cut a new 12.2.0 release and point the branch there?08:40
stephenfinYou're going to break a lot of gates if you cut a new 14.1 or 15.0 release since we've been adding jobs to test against SQLAlchemy main and oslo.db master branches, and removing those changes from oslo.db will re-break compatibility with SQLAlchemy 2.x08:41
hberaudstephenfin: I'm not sure our tooling will allow us to create a 12.2.0 from the bobcat deliverable file08:44
hberaudhowever, I agree that it would be really more easy to do that08:44
hberaudalso the problem with a 12.2.0 would be that it wouldn't solve the issue related to the version proposed with bobcat https://releases.openstack.org/bobcat/index.html#bobcat-oslo-db08:47
hberaudpeople would continue to see 13 and 14 as available for bobcat08:47
hberaudso a 15.0.0 would be required at least08:47
hberaudhowever 15.0.0 could refer to the sha to the right point on the branch08:48
hberaudas you suggested in your previous comment08:48
hberaudthoughts?08:49
stephenfinthat would work08:49
stephenfinhave you a full list of projects that are broken with oslo.db master right now?08:49
hberaudAFAIK heat, aodh, masakari, manila08:51
frickler+ cinder and maybe more, see https://review.opendev.org/c/openstack/requirements/+/87974309:04
fricklerI have prepared a series of partial reverts already, I'm going to push that anyway, then we can see which path seems easier09:04
fricklera series reverting some of the patches in 2023.2, that is, not all of them09:05
fricklerwe cannot reasonably change the root of the 2023.2 branch and releasing something for bobcat not from the head of that branch would seem very weird to me09:06
fricklerstephenfin: hberaud: ^^09:06
fricklerI did some local testing and my reverted branch at least passes with cinder and does not have additional failures with heat unit tests (there seem to be some unrelated issues there)09:08
stephenfinfrickler: that's not accurate since that bumps SQLAlchemy and Alembic also09:08
stephenfinthe autogenerated oslo.db-only patches are probably more relevant09:09
stephenfini.e. https://review.opendev.org/c/openstack/requirements/+/887261 and https://review.opendev.org/c/openstack/requirements/+/89304309:09
fricklerstephenfin: yes, but from the comment in https://review.opendev.org/c/openstack/oslo.db/+/878146 oslo.db requires sqla 2.0.5 at least?09:11
frickleralso from the above I see the same projects mostly, just ceilometer instead of cinder09:13
stephenfinI'm re-examining that this morning. I think I was wrong. Looking at it further last week, we do have some compat code to handle sqlalchemy 1.x vs. 2.x differences09:13
stephenfinI'm now thinking that the big difference is probably the removal of autocommit09:13
stephenfin(which isn't supported in SQLALchemy 2.x, but Heat, Manila etc. are still relying on it09:13
stephenfin)09:13
fricklerstephenfin: there is also the removal of oslo_db.sqlalchemy.test_migrations , see e.g. the manila failure https://zuul.opendev.org/t/openstack/build/cf97e9e6b47d43df84f5e19f64a7e21e09:17
stephenfinalso re-added that10:03
opendevreviewJiri Podivin proposed openstack/releases master: Version of the role was recently bumped in metadata  https://review.opendev.org/c/openstack/releases/+/89565412:46
fricklerttx: elodilles_pto: copying this from the oslo channel talking about whether to attach a bug report to the reverts (and their renos in particular). is there a release team bugtracker at all? would it make sense to cover both castellan and oslo.db together there?12:55
*** ykarel is now known as ykarel|away15:04
opendevreviewJay Faulkner proposed openstack/releases master: EOL ironic-prometheus-exporter stable/train  https://review.opendev.org/c/openstack/releases/+/89570216:50
JayFWhen EOL'ing multiple series for a project, do you want separate PRs for each is or one large one OK?16:52
JayFI am going to retire pike-xena of networking-generic-switch; and that can be one or 6 PRs16:52
* JayF is going to do separate PRs in lack of further guideance16:57
JayFSo I'm confused about the state of this repo: stable/pike branch exists, but it is unreferenced in deliverables. My hunch: it never got a pike release. I'm going to PR to create the yaml file and immediately EOL pike release, but I think it may end up needing manual cleanup17:11
opendevreviewJay Faulkner proposed openstack/releases master: Fix/retire networking-generic-switch pike  https://review.opendev.org/c/openstack/releases/+/89570517:13
opendevreviewJay Faulkner proposed openstack/releases master: EOL networking-generic-switch stable/train  https://review.opendev.org/c/openstack/releases/+/89570717:16
opendevreviewJay Faulkner proposed openstack/releases master: EOL networking-generic-switch stable/ussuri  https://review.opendev.org/c/openstack/releases/+/89570917:19
opendevreviewJay Faulkner proposed openstack/releases master: Fix/EOL networking-generic-switch pike  https://review.opendev.org/c/openstack/releases/+/89570517:20
fricklerJayF: likely that release was made before release automation was set up for that project. tc members should be able to also eol those manually, but best check with elodilles_pto when they're back17:21
JayFfrickler: looking at the ocata/networking-generic-swtich.yaml file, it looks similar to the one I proposed for pike17:22
JayFso I *think* merging that should do what we want and bring the yaml in line with the repo17:22
JayF(it had no automation-created releases for ocata, either)17:22
opendevreviewJay Faulkner proposed openstack/releases master: EOL networking-generic-switch stable/victoria  https://review.opendev.org/c/openstack/releases/+/89571117:23
opendevreviewJay Faulkner proposed openstack/releases master: EOL networking-generic-switch stable/wallaby  https://review.opendev.org/c/openstack/releases/+/89571217:25
fricklerJayF: oh, there's precedence for that, nice, let me check17:27
opendevreviewJay Faulkner proposed openstack/releases master: EOL networking-generic-switch stable/xena  https://review.opendev.org/c/openstack/releases/+/89571317:30
opendevreviewJay Faulkner proposed openstack/releases master: EOL python-ironicclient stable/train  https://review.opendev.org/c/openstack/releases/+/89571417:34
opendevreviewJay Faulkner proposed openstack/releases master: EOL python-ironicclient stable/ussuri  https://review.opendev.org/c/openstack/releases/+/89571717:36
JayFfrickler: btw; IDK if you picked up on it, but this is clearing zuul-config-errors for ironic17:36
JayFHappy to be part of the solution instead of the precipitate now :P 17:37
fricklerJayF: oh, indeed I didn't remember which branches were affected, but this is nice, thx17:38
fricklerinteresting, that ocata patch was even proposed by elodilles_pto , so I don't understand why we cannot use this for other pending cleanups17:39
opendevreviewJay Faulkner proposed openstack/releases master: EOL python-ironicclient stable/victoria  https://review.opendev.org/c/openstack/releases/+/89571917:46
opendevreviewJay Faulkner proposed openstack/releases master: EOL python-ironicclient stable/wallaby  https://review.opendev.org/c/openstack/releases/+/89572017:48
opendevreviewJay Faulkner proposed openstack/releases master: EOL python-ironicclient stable/xena  https://review.opendev.org/c/openstack/releases/+/89572117:50
opendevreviewJay Faulkner proposed openstack/releases master: EOL python-ironicclient stable/xena  https://review.opendev.org/c/openstack/releases/+/89572118:08
opendevreviewJay Faulkner proposed openstack/releases master: EOL networking-generic-switch stable/xena  https://review.opendev.org/c/openstack/releases/+/89571318:10

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