Monday, 2022-09-05

opendevreviewpangliye proposed openstack/releases master: Zed Cycle Highlights for Venus  https://review.opendev.org/c/openstack/releases/+/85561301:13
opendevreviewBoxiang Zhu proposed openstack/releases master: Add release liaison for Skyline project  https://review.opendev.org/c/openstack/releases/+/85584402:17
opendevreviewPranali Deore proposed openstack/releases master: Add release liaison for Glance project  https://review.opendev.org/c/openstack/releases/+/85584905:35
fricklereveryone please have a look at https://review.opendev.org/c/openstack/requirements/+/855153/comments/d1805059_3427cf26, IIUC we are in a very critcal situation, the latest oslo.db release will hard break most services.07:25
elodillesfrickler: thanks, looking!07:26
elodilleshberaud ttx : i've collected the list of deliverables with broken gates and sent this mail: https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030312.html07:27
hberaudack07:28
elodillesoh, this oslo.db thing sounds... interesting... :S07:35
elodillesas i understand some services already fixed their code to make it work with oslo.db 12.1.007:35
elodilleshberaud damani : do you have any thoughts from oslo perspective about what solution is feasible?07:37
hberaudelodilles: you mean those gates are broken by oslo?07:38
elodillesfor services we have passed Feature Freeze, but we still have time to fix bugs until RC1. the question is if this can be handled like that07:38
hberaudno idea07:39
elodilleshberaud: as i understand, yes, with latest oslo.db 12.1.0 some services gates are broken, see frickler's message above07:39
elodillesso we either revert that oslo.db patch (which is actually needed for SQLalchemy 2.0 compatibility according to the patch author) and release another oslo.db, or the services needs to fix their gates to pass with oslo.db 12.1.0 as soon as possible07:41
elodilles(let me know if i misunderstood something)07:42
hberaudstephenfin: FYI ^ this commit seems Seems it is causing widespread failures https://review.opendev.org/c/openstack/oslo.db/+/80477507:42
hberaudelodilles: no I think you are right07:43
hberauds/seems Seems/seems/07:44
hberaudHowever, the requirements bump is not yet merged07:45
elodillesyes. and it cannot be bumped until most of the services are fixed07:56
hberaudyes08:13
frickleras I wrote, afaict it took Neutron a whole cycle and I'm not sure they really found every spot. not very likely for umpteen severely understaffed projects to do the same in a couple of weeks08:20
frickleroh, I actually didn't write that, thought I did08:21
fricklerslaweq: lajoskatona: ^^ maybe one of you can share your view from the Neutron side08:22
frickleralso one more thing to note: the reqs patch only shows unit tests. many issues in neutron were only found by checking logs in real deployments, so even when all unit tests would get fixed, that's likely not the end of the story08:27
lajoskatonafrickler: reading08:30
lajoskatonaIn Neutron and stadiums some work already done, but we havent covered all08:37
slaweqfrickler: the best guy to ask about feedback with this effort is ralonsoh but he's on PTO this week08:41
lajoskatonafrickler, slaweq: our periodic unit test job with oslo.master seems to be flapping, last week as I remember we discussed it with ralonsoh, we still miss some context wrapper I think the conclusion was08:46
fricklerlajoskatona: oh, so even neutron isn't completely done, thx for that update. I have no idea whether reverting that oslo.db locking change for this cycle would be feasible, but that seems to be the only option then08:48
elodillesfrickler: according to what you wrote i tend to agree: the revert seems to be the 'least-worse' solution08:59
elodillesand add it back in Antelope cycle as soon as possible08:59
lajoskatonafrickler, elodilles: am I understand right that other projects also havent adopted fully for this change?09:12
elodilleslajoskatona: seems so09:16
fricklerlajoskatona: I'd say not at all for most of those who are failing on the reqs patch09:22
lajoskatonafrickler, elodilles: thanks09:28
hberaudwhat's about those who already migrated (over these oslo.db changes) if we revert those changes?10:29
ttxAt this point in the cycle, if only a few well-maintained projects have migrated to the new version, it will be easier to revert their migration (since they are active) than chasing down every less-maintained project to get them to fix theirs10:49
ttxBut yes we should reinsert that change early enough in the Antelope cycle10:49
*** marios is now known as marios|fooood10:50
ttxIt's a tricky call because not that many are broken, and reverting might be painful. We need a complete assessment of the two scenarios10:54
*** marios|fooood is now known as marios11:13
fricklerttx: IIUC all the changes that were made should be backwards compatible? since they work with unpatched oslo.db currently?11:14
fricklerso nothing to revert except the oslo.db patch afaict, but there may be dragons11:15
*** dviroel|out is now known as dviroel11:28
elodillesfrickler: that was my impression, too11:35
elodillesthat it's backward compatible11:35
elodillesso nothing needs to be done for those who already did the change11:36
elodillesas still the old oslo.db is used on their branch11:36
*** gthiemon1e is now known as gthiemonge12:17
*** tosky_ is now known as tosky12:23
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Xena  https://review.opendev.org/c/openstack/releases/+/85587912:38
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Yoga  https://review.opendev.org/c/openstack/releases/+/85588012:40
damanihi 12:41
damanii would like to know if eventually someone can help me here https://review.rdoproject.org/r/c/openstack/oslo-cache-distgit/+/3974412:42
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Wallaby  https://review.opendev.org/c/openstack/releases/+/85588212:45
opendevreviewHervé Beraud proposed openstack/releases master: [oslo] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85589313:48
opendevreviewHervé Beraud proposed openstack/releases master: [blazar] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85589413:51
ttxfrickler, elodilles do we have a complete list of what's broken by this change specifically?13:52
ttxIs it just what's reporting FAILURE on https://review.opendev.org/c/openstack/requirements/+/855153 ? Or is there more to it13:54
ttxOnce we have that visibility I'd recommend starting a thread specifically on oslo.db 12.1.0 and how it creates a release-blocking issue, to raise attention13:56
elodillesi don't have any list but i guess requirements doesn't test everything13:56
ttxelodilles: yeah that's my fear13:57
elodillesthough at least it tests quite many services13:57
ttxOn that thread we should propose the oslo.db revert, and see how well that flies13:58
elodillesOK, i'll try to send some summary and send it to ML, should it be tagged with [all]?13:59
elodillesi guess so13:59
ttxyeah I'd say [all][release]13:59
elodilles++13:59
ttx"[all][release] Zed release critical issue with oslo.db 12.1.0"14:00
ttxthat should attract attention14:00
elodilles++14:01
ttxtoday is labor day so we won;t have all hands on deck anyway14:04
opendevreviewHervé Beraud proposed openstack/releases master: [telemetry] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85589814:07
opendevreviewHervé Beraud proposed openstack/releases master: [OpenStackSDK] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85590214:10
opendevreviewHervé Beraud proposed openstack/releases master: [ironic] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85590314:18
opendevreviewHervé Beraud proposed openstack/releases master: [keystone] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85590414:19
elodillesttx: yepp, just wanted to mention that14:20
elodillesnevertheless, here's the mail: https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030317.html14:21
opendevreviewHervé Beraud proposed openstack/releases master: [monasca] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85590514:21
opendevreviewHervé Beraud proposed openstack/releases master: [neutron] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85590714:24
opendevreviewHervé Beraud proposed openstack/releases master: [OpenStackSDK] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85590214:27
opendevreviewHervé Beraud proposed openstack/releases master: [neutron] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85590714:28
opendevreviewHervé Beraud proposed openstack/releases master: [mistral] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85590814:30
opendevreviewHervé Beraud proposed openstack/releases master: [kuryr] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591014:31
opendevreviewHervé Beraud proposed openstack/releases master: [nova] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591114:33
opendevreviewHervé Beraud proposed openstack/releases master: [octavia] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591214:34
opendevreviewHervé Beraud proposed openstack/releases master: [heat] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591414:37
opendevreviewHervé Beraud proposed openstack/releases master: [cinder] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591514:39
opendevreviewHervé Beraud proposed openstack/releases master: [winstackers] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591614:40
opendevreviewHervé Beraud proposed openstack/releases master: [heat] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591414:41
opendevreviewHervé Beraud proposed openstack/releases master: [barbican] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591714:42
opendevreviewHervé Beraud proposed openstack/releases master: [cloudkitty] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85591814:42
opendevreviewHervé Beraud proposed openstack/releases master: [cyborg] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85592014:44
opendevreviewHervé Beraud proposed openstack/releases master: [designate] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85592214:46
opendevreviewHervé Beraud proposed openstack/releases master: [freezer] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85592314:46
opendevreviewHervé Beraud proposed openstack/releases master: [magnum] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85592414:47
opendevreviewHervé Beraud proposed openstack/releases master: [manila] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85592514:48
opendevreviewHervé Beraud proposed openstack/releases master: [masakari] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85592614:49
opendevreviewHervé Beraud proposed openstack/releases master: [murano] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85592814:50
opendevreviewHervé Beraud proposed openstack/releases master: [sahara] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85592914:51
opendevreviewHervé Beraud proposed openstack/releases master: [senlin] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85593014:51
opendevreviewHervé Beraud proposed openstack/releases master: [solum] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85593214:52
opendevreviewHervé Beraud proposed openstack/releases master: [swift] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85593314:53
opendevreviewHervé Beraud proposed openstack/releases master: [tacker] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85593414:53
opendevreviewHervé Beraud proposed openstack/releases master: [trove] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85593614:54
opendevreviewHervé Beraud proposed openstack/releases master: [venus] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85593714:55
opendevreviewHervé Beraud proposed openstack/releases master: [vitrage] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85593814:56
opendevreviewHervé Beraud proposed openstack/releases master: [zun] Create zed branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/85594014:57
*** dviroel is now known as dviroel|lunch15:32
*** marios is now known as marios|out15:51
*** dviroel|lunch is now known as dviroel16:41
opendevreviewSylvain Bauza proposed openstack/releases master: Nova Zed cycle highlights  https://review.opendev.org/c/openstack/releases/+/85597417:25
*** haleyb_ is now known as haleyb20:12
*** dviroel is now known as dviroel|out21:29

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