Thursday, 2025-01-16

opendevreviewMerged openstack/neutron-lib master: vpnaas: add support for AES CTR  https://review.opendev.org/c/openstack/neutron-lib/+/90397103:12
opendevreviewGaudenz Steinlin proposed openstack/neutron master: Fixup conntrackd support  https://review.opendev.org/c/openstack/neutron/+/93880006:08
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Reduce the OVN hash ring touch interval  https://review.opendev.org/c/openstack/neutron/+/93735106:38
opendevreviewRodolfo Alonso proposed openstack/neutron master: WIP == [OVN] ``PortBindingUpdateUpEvent``  https://review.opendev.org/c/openstack/neutron/+/93934508:14
opendevreviewRodolfo Alonso proposed openstack/neutron master: DNM - Test "neutron-ovn-tempest-ipv6-only-ovs*" with WSGI - BUG 2094736  https://review.opendev.org/c/openstack/neutron/+/93934708:27
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Reduce the OVN hash ring touch interval  https://review.opendev.org/c/openstack/neutron/+/93735109:45
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Do not fail if the ACL does not exists in the deletion  https://review.opendev.org/c/openstack/neutron/+/93440909:46
opendevreviewRodolfo Alonso proposed openstack/neutron-dynamic-routing master: Use context reader to wrap several DB operations  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/93942810:04
ralonsohykarel, hello! would you consider reviewing https://review.opendev.org/c/openstack/neutron/+/934409 again? 10:13
ralonsohbtw, I'm checking the issue wiht n-d-r (https://bugs.launchpad.net/neutron/+bug/2085421) and I don't find anything relevant10:13
ralonsohI don't know why the port deletion transaction is locked10:14
opendevreviewRodolfo Alonso proposed openstack/neutron master: [FT] Reduce arping interval in ``test_send_ipv4_addr_adv_notif``  https://review.opendev.org/c/openstack/neutron/+/93943511:45
ralonsohslaweq, ykarel ^^ trivial fix12:11
ralonsohor anyone else, thanks in advance!12:12
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron master: common: fix wait_until_true to support native thread  https://review.opendev.org/c/openstack/neutron/+/93784312:27
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron master: async_process: remove usage of eventlet for AsyncProcess  https://review.opendev.org/c/openstack/neutron/+/93934812:27
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron master: ovs: reimplement signals handling  https://review.opendev.org/c/openstack/neutron/+/93932112:27
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron master: ovs: remove the usage of eventlet in the OVS agent  https://review.opendev.org/c/openstack/neutron/+/93776512:27
sahidralonsoh: o/ regarding AsyncProcess, fi you have a moment to have a look int it https://review.opendev.org/c/openstack/neutron/+/93934812:30
sahidand btw about the signal part that we have discussed, i have started implementation here: https://review.opendev.org/c/openstack/neutron/+/93932112:31
sahidthe ovs agent does not look to use olso service with the handler thing that you mentioned, but I may have missed something12:32
sahid:-)12:32
sahidi'm trying to see how I can carticulate the change with some tests12:32
ralonsohsure, I need to finish other stuff before12:51
opendevreviewVasyl Saienko proposed openstack/neutron master: Increase ovs operation timeout for functional tests  https://review.opendev.org/c/openstack/neutron/+/93943913:00
ykarelralonsoh, ack for both13:18
opendevreviewRodolfo Alonso proposed openstack/neutron master: [FT] Reduce arping interval in ``test_send_ipv4_addr_adv_notif``  https://review.opendev.org/c/openstack/neutron/+/93943513:40
opendevreviewMerged openstack/neutron stable/2024.2: ovn: Disable activation-strategy=rarp for DPDK ports  https://review.opendev.org/c/openstack/neutron/+/93923513:56
opendevreviewBodo Petermann proposed openstack/neutron-vpnaas master: Add support for additional auth, encryption, PFS choices  https://review.opendev.org/c/openstack/neutron-vpnaas/+/89883014:09
opendevreviewRodolfo Alonso proposed openstack/neutron master: Check existence of GW port before trying to delete it  https://review.opendev.org/c/openstack/neutron/+/93945114:09
opendevreviewRodolfo Alonso proposed openstack/neutron master: Check existence of GW port before trying to delete it  https://review.opendev.org/c/openstack/neutron/+/93945114:15
opendevreviewRodolfo Alonso proposed openstack/neutron master: DNM - Test "neutron-ovn-tempest-ipv6-only-ovs*" with WSGI - BUG 2094736  https://review.opendev.org/c/openstack/neutron/+/93934714:16
opendevreviewRodolfo Alonso proposed openstack/neutron master: WIP == [OVN] ``PortBindingUpdateUpEvent``  https://review.opendev.org/c/openstack/neutron/+/93934514:35
opendevreviewRodolfo Alonso proposed openstack/neutron master: Check existence of GW port before trying to delete it  https://review.opendev.org/c/openstack/neutron/+/93945114:35
opendevreviewRodolfo Alonso proposed openstack/neutron master: DNM - Test "neutron-ovn-tempest-ipv6-only-ovs*" with WSGI - BUG 2094736  https://review.opendev.org/c/openstack/neutron/+/93934714:35
opendevreviewVasyl Saienko proposed openstack/neutron master: Increase ovs operation timeout for functional tests  https://review.opendev.org/c/openstack/neutron/+/93943914:55
ralonsohykarel, ihrachys please check https://review.opendev.org/c/openstack/neutron/+/939345. This is WIP, and is in the middle of a chain of patches. In this order:14:57
ralonsohhttps://review.opendev.org/c/openstack/neutron/+/937351/814:57
ralonsohhttps://review.opendev.org/c/openstack/neutron/+/939345/314:57
ralonsohhttps://review.opendev.org/c/openstack/neutron/+/939451/314:57
ralonsohon top of this, I've pushed a testing patch14:58
ralonsohykarel, btw, the CI is still failing due to the PG deletion. So please reconsider https://review.opendev.org/c/openstack/neutron/+/934409/1114:59
ykarelralonsoh, can you share the failures without involving 934409 i just want to ensure ovn db don't leave stale data and hide the issue15:30
ykarelcan do share over the patch, sorry i need to drop for now15:30
ralonsohykarel, for sure, and thanks!15:31
ihrachysralonsoh: tl;dr for the WIP is use pb instead of lsp (unless it's router port because these don't have pb updated or smth?) how does this scratch with the assumption that it's hash ring members losing events depending on the hash calculation (so it can either be a pb update or lsp update - but they will lose some of these nevertheless)?15:35
ihrachys(the fact Up handlers are not symmetric with Down handlers is also a concern, but probably just left out of scope for now because it's WIP I assume)15:36
ihrachyswonder if BOTH events should be handled? (this doesn't address the lost events root cause - whatever it is - but at least raises the chance that at least one will be processed? just spitballing here)15:36
ihrachysdid a test patch confirm the series is helpful?15:37
ralonsohihrachys, router ports are active when created, without any PB15:51
ralonsohihrachys, because we had problems only with up=true, I only implemented the UP event15:51
ralonsohihrachys, the test patch is still on-going, I've added more patches to the mail chain15:52
ralonsohthe test patch detected an issue with ACLs, the one I commented with Yatin15:52
ralonsohpatch related: https://review.opendev.org/c/openstack/neutron/+/93440915:52
ralonsoh(there are multiple open fronts...)15:53
ihrachysthe going theory I think is that we have problems not with lsps but with lost events in general. if so, switching from lsp to pb shouldn't do a thing. so I wonder.15:57
ihrachysand we know that this issue is wsgi env specific15:57
ihrachysthe expectation is that the maintenance thread touches hash ring nodes once in a while. but it doesn't.15:58
ihrachysdo we know that at least the eventloop is aware of the thread should be scheduled but just busy with something else for the whole minute without letting the control away? is there a way to confirm this?15:59
ihrachys(an alternative could be e.g. that the periodic is not even in consideration for some reason.)15:59
ralonsohihrachys, at least we can try increasing the timeout and reducing the refresh time15:59
ralonsoh(the patch proposed)15:59
ralonsohthat should aleviate the issue of the hash ring offline nodes16:00
ihrachysI've seen one failure where there were no logs in neutron-server for whole 2 minutes, then hash ring members went offline (there were no ovsdb-monitor event handler messages - so these did not touch nodes either) and events got lost.16:00
ihrachyscan we maybe log every time someone touches a node, with info about who did?16:00
ralonsohihrachys, in what method exactly?16:00
ihrachystimeouts - yes I agree that patch should not make it worse16:00
ralonsohthe one updating the hash ring registers in the DB?16:01
ihrachysralonsoh: in both maintenance periodic and ovsdb-monitor notify handler16:01
ihrachys(I think these are the only two who call to touch_node)16:01
ralonsohwe can directly add this message in the touch_node method16:01
ralonsohor maybe you want to add who is calling it16:02
ihrachysyeah would be nice to trace who did. we can have separate log messages in all the callers for this.16:03
ihrachysthere are not many anyway16:03
ralonsohihrachys, I'll do it tomorrow morning, I need to go leave in 2 minutes 16:04
ralonsohactually I'll do it this afternoon/night16:04
ihrachysI'll send a patch in a sec16:04
ralonsohI'll review it later16:04
ihrachysgreat. ciao, see you later.16:04
opendevreviewIhar Hrachyshka proposed openstack/neutron master: ovn: Log every time a hash ring node is touched  https://review.opendev.org/c/openstack/neutron/+/93946916:12
opendevreviewVasyl Saienko proposed openstack/neutron master: Increase ovs operation timeout for functional tests  https://review.opendev.org/c/openstack/neutron/+/93943916:13
opendevreviewIhar Hrachyshka proposed openstack/neutron master: DNM - Test "neutron-ovn-tempest-ipv6-only-ovs*" with WSGI  https://review.opendev.org/c/openstack/neutron/+/93936016:14
opendevreviewMerged openstack/neutron stable/2024.1: ovn: Disable activation-strategy=rarp for DPDK ports  https://review.opendev.org/c/openstack/neutron/+/93923617:33
haleybihrachys: do you want to merge that ovn hash ring debug change? or is more for debugging?17:56
ihrachysI think it's fine to merge it but obv it won't solve anything. assuming it doesn't blow up the size of the log files too much? let me check what it produced.18:02
* haleyb thinks you mentioned the log files yesterday, can't remember his name...18:05
haleybs/you/who18:05
ihrachysit increased size of logs by 1% in a tempest run18:06
ihrachys(size as measured in locs, not bytes)18:08
ihrachysthat said I think it's helpful; I am looking at some logs and already have some theories I think but I will have to think about these for a bit longer.18:18
ihrachysdefinitely futurist periodics doesn't get triggered in promised frequency18:21
ihrachysbut I don't think the thread is busy with anything while it's stuck18:22
opendevreviewMerged openstack/neutron master: Install DVR src to MAC flow for AAPs  https://review.opendev.org/c/openstack/neutron/+/93865721:04
opendevreviewIhar Hrachyshka proposed openstack/neutron stable/2024.2: functional: Handle ovsdb monitor returning inserts in different checks  https://review.opendev.org/c/openstack/neutron/+/93949521:25
opendevreviewIhar Hrachyshka proposed openstack/neutron stable/2024.1: functional: Handle ovsdb monitor returning inserts in different checks  https://review.opendev.org/c/openstack/neutron/+/93949621:25
opendevreviewIhar Hrachyshka proposed openstack/neutron stable/2023.2: functional: Handle ovsdb monitor returning inserts in different checks  https://review.opendev.org/c/openstack/neutron/+/93949721:26
opendevreviewMerged openstack/neutron master: ovn: Log every time a hash ring node is touched  https://review.opendev.org/c/openstack/neutron/+/93946921:56

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