Tuesday, 2025-05-20

opendevreviewBrian Haley proposed openstack/neutron-tempest-plugin master: Bump advance image to Ubuntu Jammy Server 22.04  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/94914001:06
opendevreviewBrian Haley proposed openstack/neutron-tempest-plugin master: Add test job for address_group api backend Ml2/OVN  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/90602001:13
opendevreviewBrian Haley proposed openstack/neutron-tempest-plugin master: Add test job for address_group api backend Ml2/OVN  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/90602001:16
opendevreviewMerged openstack/neutron stable/2025.1: [OVN] Create a HA_Chassis_Group without raising an exception  https://review.opendev.org/c/openstack/neutron/+/94969903:53
opendevreviewMerged openstack/neutron master: [OVN] Do not supply gateway_port if it's not bound to chassis  https://review.opendev.org/c/openstack/neutron/+/93149503:54
opendevreviewRodolfo Alonso proposed openstack/neutron-tempest-plugin master: List networks with limit and filter by provider network attrs  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/94997506:45
opendevreviewRodolfo Alonso proposed openstack/neutron-tempest-plugin master: Bump advance image to Ubuntu Jammy 22.04  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/94914007:45
opendevreviewMerged x/whitebox-neutron-tempest-plugin master: test_attach_qos_port_to_vm_with_another_port: Create VMs on different hosts  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/95029608:06
ralonsohlajoskatona, hello! I08:07
ralonsoh(sorry)08:07
ralonsohI'08:07
ralonsohahhhh08:07
ralonsohI'm going to test the DHCP agent with the oslo.service patch08:07
ralonsohMost probably, checking the code, we'll need something like this08:08
ralonsohhttps://review.opendev.org/c/openstack/neutron/+/94913508:08
ralonsohI don't know if you are working on this right now08:08
lajoskatonaralonsoh: Hi, this week I had no time for it, I have only a PoC in my local env08:23
ralonsohlajoskatona, ok so I can wait then if you already have something08:23
ralonsohfolks, please check https://review.opendev.org/q/topic:%22bug/2109354%22 if you have time08:26
lajoskatonaralonsoh: ack, thanks08:30
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] OVN agent retrieval filter matching improvement  https://review.opendev.org/c/openstack/neutron/+/94958408:30
opendevreviewRodolfo Alonso proposed openstack/neutron master: Delete the metadata agent file from the eventlet directory  https://review.opendev.org/c/openstack/neutron/+/95038408:33
opendevreviewRodolfo Alonso proposed openstack/neutron stable/2025.1: Delete the metadata agent file from the eventlet directory  https://review.opendev.org/c/openstack/neutron/+/95038508:33
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Require alembic db migration scripts to be idempotent  https://review.opendev.org/c/openstack/neutron/+/95013909:17
gibiralonsoh: lajoskatona: I see eventlet related errors in the neutron API logs in the nova CI. Could this be related to recent eventlet work?11:58
gibihttps://zuul.opendev.org/t/openstack/build/9723dbce3c0f4311881d8095d5dc347c/log/controller/logs/screen-q-svc.txt?severity=4#449911:58
gibiMay 19 13:52:48.420978 np0040808677 neutron-server[76758]: ERROR ovsdbapp.event RuntimeError: Second simultaneous write on fileno 9 detected.  Unless you really know what you're doing, make sure that only one greenthread can write any particular socket.  Consider using a pools.Pool. If you do know what you're doing and want to disable this error, call 11:58
gibieventlet.debug.hub_prevent_multiple_readers(False) - MY THREAD=<built-in method switch of greenlet.greenlet object at 0x732238af5240>; THAT THREAD=FdListener('write', 9, <built-in method switch of greenlet.greenlet object at 0x732239a11580>, <built-in method throw of greenlet.greenlet object at 0x732239a11580>)11:59
lajoskatonagibi: anything can happen :-)12:07
ralonsohgibi, let me check12:29
gibithanks12:30
ralonsohgibi, why is Nova still using the eventlet server??12:32
ralonsohlet me check the devstack config12:32
ralonsohgibi, https://review.opendev.org/c/openstack/devstack/+/93219912:40
ralonsohI was looking for something related12:40
ralonsohsince 7 hours ago, the default Neutron server will be WSGI, not the eventlet that is on these logs12:40
ralonsohso we don't need to change any job definition12:41
opendevreviewRodolfo Alonso proposed openstack/neutron master: [FT] Check the SB Port_Binding is created before test execution  https://review.opendev.org/c/openstack/neutron/+/95040812:48
haleyb#startmeeting networking13:00
opendevmeetMeeting started Tue May 20 13:00:35 2025 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
opendevmeetThe meeting name has been set to 'networking'13:00
haleybPing list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh13:00
mlavalle\o13:00
mtomaskao/13:00
ralonsohhello13:00
ykarelo/13:00
rubasovo/13:00
obondarevo/13:00
haleybalright we can get started13:01
lajoskatonao/13:01
haleyb#announcements13:01
haleybWe are currently in Week R-18 of Flamingo13:01
haleybwe just completed Flamingo-113:02
haleybOur next milestone in this development cycle will be Flamingo-2, on July 3rd13:02
haleybThis milestone is when we freeze the list of deliverables that will be included in the 2025.2 Flamingo final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/flamingo directory of the openstack/releases repository13:02
haleybFinal 2025.2 Flamingo release: October 3rd, 202513:03
haleyb#link https://releases.openstack.org/flamingo/schedule.html13:03
haleybReminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers13:03
haleybthe meeting last week was canceled, i will look at new rfes for this week13:04
bcafarellate o/13:04
haleybas i was out last week and only worked a few hours, any fires i should be aware of? i didn't see anything on the ML or irc backtrace13:04
ralonsohnothing urgent/critical13:05
haleyback, thanks for taking care of the place :)13:05
haleybi had no other announcements, anyone else have something?13:06
haleyb#topic bugs13:06
haleybbcafarel was the deputy last week, his report is at13:06
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/GCVMPXGHVV535VPUNYP2LUDM6PKBKV5W/13:06
haleybnot too many bugs13:06
bcafarelI got lucky it seems :)13:07
haleyband it looks like most got an owner and a patch13:07
haleybthere was only one CI-related one13:08
haleyb#link https://bugs.launchpad.net/neutron/+bug/211087813:08
haleybonly seen once13:08
ralonsohI'll check it today 13:09
haleyback, thanks13:09
haleybany other bugs to discuss?13:09
mtomaskaI forgot to include one bug in my last week report. https://bugs.launchpad.net/neutron/+bug/211008513:09
haleybthat might be a duplicate?13:10
haleybralonsoh: that one looks like something you've been working on?13:10
tridentAny chance there could be some eyes on https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1924776 - If I have not misunderstood something, this kind of limits the use of address scopes with OVN pretty severely as it doesn't honor address scopes when taking the decision of using NAT or not between two networks connected to a router as I think it should.13:10
mtomaskaDuplicate? I have to look, but I feel like this is known issue13:10
ralonsohmtomaska, are there any logs?13:10
mtomaskano13:11
slaweqo/ sorry for being late13:11
mtomaskaexcept what is in the bug already13:11
ralonsohok, let me check that out of this meeting13:12
ralonsohI'll assign this one to me13:12
haleybtrident: that seems like an old bug, does this still happen on master branch?13:12
mtomaskaI feel like this was discussed somewhere that uwsgi is only single threaded.... or I might be confusing with something else. 13:13
haleybtrident: we can discuss after meeting13:13
lajoskatonaisn't that related to what gibi posted few hours back ? (https://meetings.opendev.org/irclogs/%23openstack-neutron/%23openstack-neutron.2025-05-20.log.html#openstack-neutron.2025-05-20.log.html#t2025-05-20T11:58:47)13:13
lajoskatonaI mean the wsgi thing?13:14
ralonsohlajoskatona, no, this one is using eventlet server13:14
lajoskatonaoh no that is something eventlet13:14
lajoskatonaralonsoh: yeah, ack13:14
ralonsohthe bug reported is using wsgi13:14
tridenthaleyb: Ok, thanks!13:14
ralonsohtrident, haleyb I tried last week to make this feature work13:14
ralonsohwithout any success13:14
ralonsohso I think this is not supported in ml2/ovn (I'm not saying in OVN, just could be a bad implementation in Neutron)13:15
ralonsohSo I think the bug is legit13:15
haleybyes, i remember you doing some address scope testing13:15
ralonsohrelated to another feature, yes13:15
ralonsohlet's talk after the meeting13:15
haleyback13:16
opendevreviewLajos Katona proposed openstack/os-vif master: VS Trunk: Add bridge_name to external_ids  https://review.opendev.org/c/openstack/os-vif/+/94973613:16
haleybthis week the deputy is elvira, next week is slaweq - does that work for both of you?13:16
haleybok, i will ping people again later13:18
haleyb#topic community goals13:18
haleyblajoskatona: any update on neutronclient changes?13:18
slaweqyeap13:18
lajoskatonayes, 13:18
lajoskatonayesterday I found (thanks for reviewers in horizon) that in SDK there is no shared field for sec-groups: https://review.opendev.org/c/openstack/openstacksdk/+/95030513:19
elvira(yes, it works, sorry for the late answer o/)13:19
lajoskatonaand pushed also a patch for QoS: https://review.opendev.org/c/openstack/horizon/+/94976413:20
haleybelvira, slaweq - thanks13:20
lajoskatonabut no time for fullstack vs SDK patch (the no-auth problem) :https://review.opendev.org/c/openstack/neutron/+/94785113:21
haleyblajoskatona: thanks! i've started watching both13:21
lajoskatonathat's it for neutronclient13:21
haleybgreat, thanks for the update13:21
lajoskatonasome CI is failing I have to go back to see what I broke13:21
haleyback13:21
haleybralonsoh: and finally eventlet13:22
ralonsohnothing new in gerrit13:22
ralonsohI've started with the migration of the tests, but locally 13:22
ralonsohplease check https://review.opendev.org/c/openstack/neutron/+/94913513:22
ralonsohsomething similar will be needed for the DHCP agent13:23
ralonsohthat's all13:23
haleyback, thanks, will look13:23
lajoskatonaI work on the dhcp agent13:23
ralonsohlajoskatona, thanks!13:24
haleybralonsoh: there was one change that Liu was having an issue with, do we need to discuss that further? i'd have to find the link13:24
ralonsohone sec13:24
ralonsohhttps://review.opendev.org/c/openstack/neutron/+/94820013:24
ralonsohnow with functional tests13:24
ralonsohwe can talk about this one in the on-demand section13:25
ralonsohactually, I would like to bring it back13:25
lajoskatonabut for that topic there are patches from Liu also: https://review.opendev.org/q/topic:%22bug/2106463%2213:25
haleybralonsoh: i can start on-demand13:26
haleyb#topic on-demand13:26
ralonsohlajoskatona, yes, I also mentioned that the DB constraint introduced is against what we consider a tunnelled network13:27
opendevreviewMerged openstack/neutron-lib master: api-ref: Add warning about DRA scheduler  https://review.opendev.org/c/openstack/neutron-lib/+/94974413:27
ralonsohfor any tunnelled network, the physical network is None, not an empty string13:27
ralonsohand as I commented, my patch is backportable, fixes the problem with multiple workers (this is now executed in the first one only)13:27
ralonsohand works for multiple servers booting at the same time13:28
haleybralonsoh: is there any merit to also doing the DB constraint going forward? although it's not necessary with all your code13:29
ralonsohit is not necessary this db constraint13:29
ralonsohI also remember trying to introduce something similar years ago13:29
haleyback13:30
ralonsohin any case, if we want the constraint added, it could be on top of my patch13:30
haleybyes, not instead of, on-top for now and future13:31
ralonsohno problem **IF** we don't add an empty string for tunnelled networks in the physical network13:31
haleybwe need to backport13:31
ralonsohyes, my patch is enough and backportable13:31
haleybso i guess we can wait for his response, i also do not understand13:32
opendevreviewMerged openstack/neutron-lib master: api-ref: Remove crud from conf.py  https://review.opendev.org/c/openstack/neutron-lib/+/94974513:32
ralonsohI have another quick topic13:33
ralonsoh#link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/94914013:33
ralonsohI addressed yatin's comment: I'm using ubuntu server only in OVN, due to the issues with IGMP 13:34
ralonsohabout lajoskatona's comment: the issue is that using Focal VM is a problem in the CI13:34
lajoskatonaralonsoh: ack, checking13:34
ralonsohI understand the logic of this comment: do not change what is working13:34
haleybralonsoh: yes, we should move to jammy or jammy server13:35
ralonsohbut the problem is that we are hitting some errors in the CI with focal image13:35
ralonsohhaleyb, I've used both13:35
ralonsohminimal by default, server only in ovn (for IGMP)13:35
haleybah, ok, one is the minimal now13:35
ralonsohwith a note to go back to minimal if there is a fix13:35
ralonsohand that's all, thanks!13:36
haleyback, thanks, i did start watching that bug too13:36
haleybso last on-demand topic is mine13:37
haleybi created backports for a patch that landed in 2025.113:37
haleyb#link https://review.opendev.org/c/openstack/neutron/+/85150913:37
haleyb#link https://bugs.launchpad.net/neutron/+bug/198228713:38
haleybthe bug was added as an rfe13:38
haleybsince the dependend ovsdbapp code landed in 2024.1 i wanted to backport this neutron fix to there as well13:38
haleybi do understand ralonsoh's point last week that this was a feature, but i feel it was something missed13:39
ralonsohif we accept these backports, I would change the reno from "feature" to "other" in the stable branches13:40
haleybralonsoh: i am relating this change to the one we did for ovs hybrid driver13:40
haleyb#link https://review.opendev.org/c/openstack/neutron/+/91370813:40
haleybthat one we backported from 2024.1 to yoga13:41
haleybso i wanted to get other opinions on the OVN one13:41
haleybi did find a tempest patch that never merged to test it all, which i have updated13:41
haleyb#link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/90602013:41
ralonsohI'm ok, but let's change the reno to avoid the wrath of release team. I would add something like "testing feature"13:42
haleybthat seems to have failed miserably overnight13:42
haleybralonsoh: ack, i can update the release note on the backports13:43
lajoskatonaThe RFE label is really a headsup thing but as I understand this patch fixed the OVN backend13:43
haleybi am worried about why the n-t-p change took a turn, but will have to look at logs13:43
lajoskatona+113:43
ralonsohyeah, lets make the n-t-p patch work with the dependencies to the backports13:44
haleybonce the backports merge i will update n-t-p to test on those branches13:44
haleybralonsoh: sure, i could do that as well13:44
ralonsohjust to test before merge13:44
haleybi will do that right after meeting, is related to something hot downstream13:45
haleybthanks for the discussion everyone13:45
haleybthat was all the topics, anything else to discuss?13:46
haleybok, thanks for attending everyone, have a great week13:46
haleyb#endmeeting13:46
opendevmeetMeeting ended Tue May 20 13:46:33 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:46
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2025/networking.2025-05-20-13.00.html13:46
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2025/networking.2025-05-20-13.00.txt13:46
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2025/networking.2025-05-20-13.00.log.html13:46
mlavalle\o13:46
lajoskatonao/13:46
bcafarelo/13:46
ralonsohbye13:46
* bcafarel adds backport to the review list (if it's "optimisation" using direct OVN existing for address sets, can be good to hvae)13:47
ralonsoh+113:47
tridentralonsoh, haleyb: I have not recently tested with master, but seems like you have confirmed https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1924776 is still around ralonsoh?13:48
haleybbcafarel: remote address groups in SGs doesn't work in OVN without that fix, i've tried :(13:48
ralonsohtrident, yes, that doesn't work for me in master13:48
haleybbcafarel: well, on caracal that is, it works on 2025.113:48
haleybcaracal is this important LTS release people like :)13:49
tridentI am pretty much trying to replicate the behaviour with ml2/ovs, the most common use case here is for IPv6, where the "link" network on ext-net and tenant networks created from IPv6 pool is doesn't use NAT as well as being BGP announced. While a tenant network with a random IPv6 prefix won't get announced. But we use it here and there for IPv4 as well.13:51
bcafarelhaleyb: ack, so it sounds useful to have backported if possible :)13:51
haleybbcafarel: yes, i'd put it on the OVN/ML2-OVS gap category13:52
tridentIt can be somewhat worked around by manually setting the snat flag, but if a router has one subnet connected that should do NAT and one that shouldn't I guess that won't work. Also the BGP announcement filtering can be somewhat worked around as well by manually specifying the address scopes that should be announced, but that is not so dynamic.13:52
haleybtrident: IPv6 shouldn't use NAT either way we don't support it in neutron13:53
tridenthaleyb: Hm, true. Then for IPv6 it's only the issue of only BGP announce tenant subnet prefix:es created from a subnet pool in the same address scope as ext-net:s IPv6 subnet.13:56
tridenthaleyb: But for IPv4 both the issues are present.13:58
haleybtrident: ack, can you add that info to the bug? and any other steps you've used to recreate if not already there13:58
tridentAnd there should probably be another bug for using address scopes to dynamically announce or not announce prefixes like dragent does. Will look into filing such a bug as well.13:59
tridentAs they are really separate issues.14:00
tridenthaleyb: Yes. I'll look into what more information I can provide in the bug. (I was not the initial reporter).14:00
haleyb+114:04
dansmithI'm trying to get a local multinode devstack install running and I need actual networking to do my test, but I'm struggling with neutron14:11
dansmiththe issue I'm hitting looks like this unfixed bug: https://bugs.launchpad.net/neutron/+bug/181650214:11
dansmithhere's my actual failure: https://paste.opendev.org/show/bzjEWeg3yo6nPQ1qNHpQ/14:11
dansmiththat seems really odd because I would not expect a 500 and a huge stack trace in the server logs from something a user does if it's just mis-specifying a prefix or something14:12
dansmithcan someone help?14:12
dansmithlocalrc content relevant to neutron is: https://paste.opendev.org/show/buLgNKNZsgTW2U2vxyZQ/14:13
gibiralonsoh: OK, so something does changing and we expect that after the wsgi change in devstack this will not happen again. Thanks. I will report back if I see this again in the future14:17
ralonsohgibi, for sure and thanks for checking14:17
ralonsohdansmith, let me check14:17
ralonsohdansmith, do you have the Neutron API logs?14:20
dansmithralonsoh: yeah, how much do you want to see? there's a massive traceback in there14:21
ralonsohjust during the subnet creation14:22
ralonsohwhat version are you using?14:22
dansmithhere's a big chunk: https://paste.opendev.org/show/b2FyWVYNnOPAdjjsnDoP/14:22
dansmithversion? of neutron? 993ada3ecc Remove installation guide for openSUSE/SLES14:23
ralonsohso almost the last one (if not the last)14:23
dansmithright14:24
dansmithit's devstack, so master14:24
ralonsohdansmith, the network GW 192.168.122.135 is not in the range of 192.168.122.0/2614:30
dansmithralonsoh: okay tbh, I don't understand what I'm supposed to be giving it.. I thought 122.0/16 is the chunk of the existing network that neutron can hand out on its own14:31
ralonsohdansmith, not 122.0/16, you wrote 122.0/2614:31
dansmithi.e. FIXED_RANGE= needs to be unallocated to other stuff right?14:31
dansmithralonsoh: right, sorry, typo14:31
ralonsohdansmith, this is a private network, it won't be connected to a host network14:32
ralonsoheven if the IPs are the same14:32
dansmithokay I'm super confused about all the things in the localrc then.. seems like there's not a lot of good documentation about what those need to be so I pieced together from a CI job14:32
dansmithIPs in FIXED_RANGE= are not going to be used for anything?14:32
ralonsohdansmith, you have the PUBLIC_NETWORK_GATEWAY, that could be an IP of you host, if you can route the traffic from there14:33
dansmithralonsoh: I have two boxes on the same L2, one devstack master, one devstack compute node.. I just need to be able to spin up instances on either and be able to ssh into them.. that L2 is 192.168.122.0/24 14:34
dansmithcan you just explain what I need to set the localrc things to?14:34
ralonsohfixed range is of the private network, it could be anything14:34
ralonsohdansmith, you need to have connectivity for the services, using this 192.168.122.0 network. And then you need to create the underlaying network for the user traffic14:36
ralonsohIt would be better if you check a multinode deployment in zuul14:37
ralonsohlet me check14:37
dansmithralonsoh: based on what I said above, is this right? https://paste.opendev.org/show/btoV4MPyLET5tzWzjfva/14:37
dansmithralonsoh: I've looked at them in zuul conf, but it's hard to know which networks are which just from that.. that's what I startedf rom14:37
ralonsohdansmith, the NETWORK_GATEWAY variable is the private network GW IP. This is not the same as PUBLIC_NETWORK_GATEWAY14:38
ralonsohthe NETWORK_GATEWAY will be used for the tenant networks14:38
dansmithso does that need to be an IP on the 172.16.0.0 network?14:38
ralonsohthat could be anything14:38
ralonsohyes14:38
dansmithack14:38
ralonsohalso be aware of the floating IP range14:39
ralonsoh0./26 does not contain 122.13514:39
ralonsohhttps://www.calculator.net/ip-subnet-calculator.html?cclass=any&csubnet=26&cip=192.168.122.0&ctype=ipv4&x=Calculate14:39
dansmithyeah, I know it doesn't.. how can it?14:39
opendevreviewIvan Anfimov proposed openstack/neutron master: Remove code for suse from post-devstack installation  https://review.opendev.org/c/openstack/neutron/+/95036414:39
dansmithif it does, won't neutron try to re-assign that IP, or the IP of other things there? I was trying to give it a routable segment that won't have other things assigned14:40
dansmithboth devstack boxes will have an IP there14:40
ralonsohno, the public network GW IP is an external IP14:40
ralonsohthat won't be in Neutron, ever14:40
ralonsohNeutron won't create a port with this IP in the external network14:41
dansmithokay so 192.168.122.0/24 and it will exclude 135 because PUBLIC_NETWORK_GATEWAY ?14:41
ralonsohyes14:41
dansmithhow does neutron know to exclude the compute node, which might be .136 ? or the dhcp server which might be .200 ?14:41
ralonsohonce created the env, try to create a port with this IP14:41
ralonsohthis is an external network14:42
ralonsohyou need always to be careful with it14:42
ralonsohyou can have this (one sec)14:42
ralonsohdansmith, 14:43
ralonsohhttps://paste.opendev.org/show/b12vKW9b2cAZzeeLZPsF/14:43
ralonsohallocation pools14:43
dansmithah, is that what IPV4_ADDRS_SAFE_TO_USE sets?14:44
ralonsohthat means: Neutron will assign an IP address on this pool, that could be a reduced set of the subnet range14:44
ralonsohlet me check devstack14:44
ralonsohSUBNETPOOL_PREFIX_V4=${SUBNETPOOL_PREFIX_V4:-$IPV4_ADDRS_SAFE_TO_USE}14:44
ralonsohexactly14:44
dansmithokay so: https://paste.opendev.org/show/bgF6zrB26MnOBpYbFZP9/14:44
dansmithfloating covers the whole subnet, but SAFE_TO_USE is only the first chink14:45
dansmith*chunk14:45
ralonsohyes14:45
dansmithokay I'll give that a shot, thanks for your help, sorry for the dumb questions14:45
dansmithhowever, seems like this should not generate a 500 and stack trace, no?14:46
ralonsohnot this config, I think14:47
ykarelralonsoh, dansmith i recall seeeing this error14:48
ykareliirc restart fixes this, so something during initialization missed14:48
dansmithmy point is, it should be "400: User did omething wrong" not "500: server crashed"14:49
ykarelrestart neutron api14:49
ralonsohdansmith, in this particular config, the problem was that the GW IP was not in the range of the subnet14:49
ralonsohykarel, ^14:49
ykarelit's not user thing, but initialzation issue on server14:49
dansmithralonsoh: no, I understand, but that's a client error (4xx) not a server error (5xx)14:49
ralonsohyes... that's a weird error14:50
dansmithI am the user here, I screwed up, so it should be 4xx14:50
ralonsoh"let me try this at home"14:50
dansmithI came here because 5xx tells me "neutron screwed up" :P14:50
ykarelokk after re reading the error, i see it's not the same issue that i recalled14:51
ykarelso ignore me14:51
slaweqralonsoh dansmith I always have this explanation in my head when it is about HTTP codes: https://www.reddit.com/r/ProgrammerHumor/comments/2rttnv/http_status_ranges_in_a_nutshell/ :)14:52
ralonsohhehehe correct!14:52
dansmithslaweq: exactly :)14:52
dansmith"5xx: file a bug and ping ralonsoh on IRC to fix" ... "4xx: ping ralonsoh on IRC to see what you did wrong" :)14:53
ykarelwe have some multinode devstack config https://github.com/openstack/neutron/tree/master/devstack for both ovs/ovn14:53
ykarelnot sure how up to date these are though14:53
slaweqwe should fix it14:55
slaweqand I agree that in any case it shouldn't be 500 what's returned to user14:55
slaweqIM14:55
slaweqIMO14:55
ralonsohdansmith, confirmed: if you use a subnet pool and you try to assign a GW IP that cannot be retrieved from the subnet pool (because is out of range or this range is already used)14:57
ralonsohthat will return a HTTP 500 SubnetAllocationError14:57
dansmithack14:57
dansmithconsistency is good at least :)14:57
lajoskatonaralonsoh: for eventlet + oslo.service: I think I can push tomorrow wip patches (like I saw it working)15:03
ralonsohlajoskatona, cool!15:03
ralonsohcould you first push the RPC change independently?15:03
ralonsohthat should work with and withoyt eventlet15:03
lajoskatonaralonsoh: but, I have to add oslo.service.backend.init_backend(backend.BackendType.THREADING) somewhere here: https://opendev.org/openstack/neutron/src/branch/master/neutron/agent/dhcp_agent.py#L2215:03
lajoskatonaotherwise I have eventlet15:04
ralonsohlajoskatona, not there, in the agent15:04
ralonsohone sec15:04
lajoskatonayes that's good idea to have that in separate change15:04
ralonsohlajoskatona, https://review.opendev.org/c/openstack/neutron/+/938404/17/neutron/cmd/agents/l3.py15:04
ralonsoh(in the dhcp one, of course)15:04
ralonsohthis is the first code executed15:05
lajoskatonaralonsoh: ohh, I see, I move it there than15:07
dansmithoye, ralonsoh same issue when I restack.. the /26 got used on the subnet again for the prefix, so there must be more devstacky stuff going on15:07
ralonsohdansmith, please, send me the devstack and neutorn logs15:07
ralonsohI need to go now, but I'll check them later15:08
ralonsohyou can send it in private15:08
*** ralonsoh is now known as ralonsoh_out15:08
dansmithSUBNETPOOL_PREFIX_V4=${SUBNETPOOL_PREFIX_V4:-$IPV4_ADDRS_SAFE_TO_USE}15:09
dansmithit uses the safe-to-use for the prefix as well, not FLOATING_RANGE apparently15:09
opendevreviewMerged openstack/neutron stable/2025.1: [OVN] Only update the MTU of the router GW LRPs  https://review.opendev.org/c/openstack/neutron/+/94913615:22
opendevreviewMerged openstack/neutron stable/2024.1: AddressGroup API collection should be the resource name in plural  https://review.opendev.org/c/openstack/neutron/+/94997216:03
*** jcosmao is now known as Guest1642319:26
opendevreviewBrian Haley proposed openstack/neutron stable/2024.2: [OVN] Support address group for ovn driver  https://review.opendev.org/c/openstack/neutron/+/94985219:37
opendevreviewBrian Haley proposed openstack/neutron stable/2024.1: [OVN] Support address group for ovn driver  https://review.opendev.org/c/openstack/neutron/+/94985419:38
opendevreviewBrian Haley proposed openstack/neutron-tempest-plugin master: Add test job for address_group api backend Ml2/OVN  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/90602019:43
haleyb_mlavalle: not sure if you're around, but can you take a look at https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/949140 ?21:00
haleyb_gate seems worse since this morning21:00

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