Friday, 2026-01-09

opendevreviewyatin proposed openstack/neutron master: [DNM] Check migration ovn  https://review.opendev.org/c/openstack/neutron/+/97282004:44
-opendevstatus- NOTICE: Zuul is up and running again and should report back to Gerrit successfully. Changes can also merge if there are no other failures, but we expect that publication jobs like docs and tarballs updates will not work currently.05:02
*** ykarel_ is now known as ykarel05:36
ykarelhaleyb, ack06:15
opendevreviewRodolfo Alonso proposed openstack/networking-bgpvpn master: Change test code to use project_id key  https://review.opendev.org/c/openstack/networking-bgpvpn/+/97222607:07
opendevreviewBrian Haley proposed openstack/networking-bgpvpn master: Remove py312 jobs from check and gate queue  https://review.opendev.org/c/openstack/networking-bgpvpn/+/97278607:07
opendevreviewThéo Van Gyzel proposed openstack/neutron master: Fixed: network object was not updated after calling the enable driver while configure DHCP for a network  https://review.opendev.org/c/openstack/neutron/+/96232310:27
opendevreviewDaniel Failing proposed openstack/neutron master: Improve OVNGatewayLeastLoadedScheduler runtime  https://review.opendev.org/c/openstack/neutron/+/96782710:42
theovglajoskatona haleyb Hey! Sorry for the bother but it looks like PEP8 didn't break during verification but did during gate tests... I fixed it real quick if you could re-approve the change it would be appreciated, thank you! https://review.opendev.org/c/openstack/neutron/+/96232312:19
lajoskatona theovg: no problem, some changes happened around pep8 so perhaps you run into that12:35
theovgThanks! :)12:35
*** root is now known as Guest3549013:55
mlavallehaleyb: are we meeting today?14:00
haleybmlavalle: yes, just slow getting to desk14:00
haleyb#startmeeting neutron_drivers14:01
opendevmeetMeeting started Fri Jan  9 14:01:29 2026 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'neutron_drivers'14:01
haleybPing list: ykarel, mlavalle, mtomaska, slaweq, tobias-urdin, lajoskatona, haleyb, ralonsoh14:01
ralonsohhello14:01
mtomaskao/14:01
mlavalle\o14:01
haleybhi everyone, happy Friday :)14:02
haleybi see we have two agenda items14:02
slaweqo/14:03
haleybfirst is from ralonsoh regarding OVN live migration14:03
ralonsohthanks14:03
haleyb#link https://bugs.launchpad.net/neutron/+bug/206971814:03
ralonsohIn a nuthsell: we have problems with the live migration14:03
lajoskatonao/14:03
ralonsohin loaded compute nodes, if the ovn-controller does not have time to setup the OF rules, there will be a network disruption14:04
ralonsohthe TAP device is created when the VM is unpaused14:04
ralonsohso, sean-k-mooney is now implementing a patch in os-vif to pre-create the TAP device 14:04
ralonsohin that case, libvirt won't need to do it in the unpause command14:05
ralonsoh#link https://review.opendev.org/c/openstack/os-vif/+/97123114:05
ralonsohfrom Neutron, we would like this to be configurable14:05
ralonsoh#link https://review.opendev.org/c/openstack/neutron/+/97203914:05
haleybjust to make sure we don't break something?14:05
ralonsoh^^ this patch requires an extra patch in Nova to parse this new binding variable14:06
ralonsohhaleyb, yes, to make it false by default14:06
ralonsohbut if that works the best strategy will be to enable it by default, but first let's test it14:06
ralonsohand the last part from Neutron:14:06
ralonsohto be able to send the vif-plugged event when OVN adds the additional chassis to the port binding14:07
ralonsoh#link https://review.opendev.org/c/openstack/neutron/+/95691014:07
ralonsoh^^ this patch requires Nova compute/os-vif to pre-create this TAP device14:07
ralonsohso basically this is what we are trying now14:07
slaweqralonsoh if that will work, what's the point of having it configurable? Are there any downsides of enabling it?14:07
mtomaska^ I was wondering about the same14:08
ralonsohslaweq, just to enable by default the current behaviour14:08
ralonsohthere are other platforms (DPDK, HW offloaded) that are not tested14:08
ralonsohand we don't know the behaviour14:08
ralonsohthat was just a heads-up of what is happening there14:10
haleybis plan to merge this cycle?14:10
ralonsohwell, I would like that but Nova is also involved14:11
slaweqso maybe, instead of having new config knob we could try to test this new behavior on different platforms as much as we can and if there would be no "hard" conditions why it has to be done in old way on some of the platforms, then simply use new approach everywhere. If there will be some issues with it we can always treat it as a bug, no?14:11
ralonsohI really would like to haver it this cycle14:11
ralonsohslaweq, the idea is to initially test it locally in the CI14:11
ralonsohit could be enable by default and wait for the bugs later14:12
haleybi guess i tend to agree with slawek to maybe enable by default, since there will be a config option it can be disabled if an issue is found14:13
slaweqok, we can do it in couple of steps: first have it configurable and maybe even enabled by default, but then remove the config option at some point if it will be working fine14:13
ralonsohthe config option is just a safeguard to avoid disruptions in other envs14:13
ralonsohit can be enabled/disabled quickly14:14
slaweqif can be done quickly but it means that we need to maintain 2 different code paths just because in one of them there may be a bug :)14:14
ralonsohok, I'll talk to sean-k-mooney about this14:15
slaweqI think that if we will decide to go with config option, it should be temporary solution (safeguard) and final goal should be to switch to new solution and remove config option then14:15
haleybright. i guess i see more downstream work if not enabled by default, just to enable it in two installers :)14:15
haleyband if we want to enable by default i guess we should do this cycle in neutron, as it's a new option14:18
lajoskatonaif we enable by default in neutron will that affect Nova also?14:18
lajoskatonaeven if nova work is not merged , or that is not possible<14:19
lajoskatona?14:19
haleybright, and without the os-vif code does the option do anything? i haven't looked at code yet14:19
ralonsohnot yet14:19
ralonsohthe os-vif patch makes the change unconditionally14:19
ralonsohit was agreed to have this knob in Neutron and I commented that in the os-vif patch 14:19
sean-k-mooneyfor hardware offload14:20
sean-k-mooneywe don not use taps nor for dpdk14:20
sean-k-mooneyso this would only be done for vanilla kernel ovs14:20
sean-k-mooneyfor hardware offloaded ovs we are adding the representor vf during plugging already14:21
sean-k-mooneyso that shoudl not be impacted14:21
sean-k-mooneyfor vhos-user ovn need to be able to compute hte flows without the of-port bring assigned14:22
ralonsoh^^ how is that??14:22
sean-k-mooneyfundementlly that is the reguression form ml2/ovs ot ml2/ovn14:22
ralonsohwe can talk later, maybe14:22
sean-k-mooneysure14:22
ralonsohso basically the knob is necessary right now (I would need to change the patch only to include it in vanilla ovs porbinding )14:23
sean-k-mooneythe reason we need the knob is really for live migration in a mixed upgraded env14:24
sean-k-mooneyso it can be intoduced as deprecated14:24
sean-k-mooneyand dropped in 2026.214:24
sean-k-mooneywell if nova raises it min os-vif version. we can dicusscus this more sperately if you like14:25
slaweqsean-k-mooney ++ that is what I was talking about, thx14:25
slaweqso we don't need to keep that knob forever14:26
slaweqthx14:26
haleybso is there a nova patch as well?14:26
sean-k-mooneythere will be when i write it14:26
haleyb:)14:26
sean-k-mooneyim currently setting up a 2 node devstack to devleop and test htis14:26
sean-k-mooneythe nova patch is tweakign the xml generation if the flag is set in the neutron vif binding:details field and passing the flag to os-vif14:27
sean-k-mooneyso that shoudl be pretty simple14:27
sean-k-mooneyi should have that ready in the next day or two.14:28
haleybok, should we vote on approving this for neutron?14:30
haleybor are there other questions?14:30
lajoskatonano question from me14:31
mlavallei'm ok with it14:31
haleybmy network blipped, thought i was disconnected for a second14:31
haleyb+1 from me14:32
mlavalle+114:32
mlavalleto formalizae my vote14:32
slaweq+114:32
lajoskatona+114:32
ralonsohthank you all for your time, I hope this time we'll improve even more the live-migraiton14:32
haleybi'll mark it approved, thanks for working on it ralonsoh and sean-k-mooney 14:33
haleybthere was one other agenda item from mtomaska 14:34
haleyb#link https://bugs.launchpad.net/neutron/+bug/213522814:34
mtomaskaI added more details in comment#214:34
mtomaskabut in a nutshell. This is more of a "debug tool". A user will be able to create a local port which will contain mirrored traffic from one or more VM ports on the same chassis14:35
lajoskatonaI wrote in comment that what sounds interesting is the mirroring of offloaded traffic can be most interesting 14:35
mtomaskaI feel like this will be only useful on environments where you can not directly attach tcpdump to a vm port. I.e. OVN-DPDK14:36
sean-k-mooneyyou can do a tcp dump usin gthe ovs dpdk tooling14:37
sean-k-mooneythey have a commnad for that14:37
haleybovs-tcpdump, but i don't know if it works for ovn dpdk?14:37
slaweqit sounds good for me. The only small comment I have is that maybe it should be allowed to admin user only by default because IIUC owner of the port (regular user) will not benefit from creating such mirror as will not have access to the compute node, right?14:38
sean-k-mooneywell the toole work with dpdk ports in genreal i belive14:38
mtomaska@slaweq, good point14:38
lajoskatona+1 for admin user14:39
mtomaskais ovs-tcpdump available in default installation?14:39
haleybit's typically in openvswitch-switch package14:40
haleybit basically makes a clone of an OVS port so tcpdump can work14:40
mtomaskayes14:40
sean-k-mooneyit was created specificly to allwo you to use ovs-dpdk with tcpdump yes14:41
mtomaskabut if admin can use ovs-tcpdump and they prefer it, then maybe this RFE does not provide much value?14:41
sean-k-mooneyovn shoudl not really impact that as this is workign at the ovs level with that said i have not tested that14:41
ralonsohmtomaska, I was going to ask this14:42
ralonsohif you can provide extra functionalities, maybe that could be useful14:42
sean-k-mooneymtomaska: my main concer looking at it privly was that it woudl imply that the ports on the vswitch are exposed via the rest api14:42
haleybi'm also not sure it can see dpdk traffic, would have to verify14:43
sean-k-mooney`openstack tap mirror create --port some_vm_port --name other-vm --directions BOTH --mirror-type local --local-mirror-port my-vm`14:43
ralonsohhaleyb, yes it does14:43
haleybmtomaska: we use ovs-tcpdump in our internal clouds here14:43
sean-k-mooneyso if it was not admin only user could do ^14:43
sean-k-mooneyfor vms form other tenants14:43
sean-k-mooneyi thinki mixed up --port and --name in that example but you get the point14:44
mtomaskaSean, we would implement some SRBAC to limit port mirror creation14:44
mtomaskano :)14:45
sean-k-mooneyexposing the ablity to specify vswitch prot names is problematic14:45
mtomaskaare you saying that someone would be able to "redirect" traffic from one vm to another? 14:45
sean-k-mooneyyes or monitor it14:45
sean-k-mooneyi know that is what tap as a service is for14:46
opendevreviewEduardo Olivares proposed x/whitebox-neutron-tempest-plugin master: [multicast] Only use vlan_transparent option when really required  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/97289914:46
sean-k-mooneybut if you are exposing the actul vswich port names in the api14:46
sean-k-mooneythat causes multi teancy problems14:46
mtomaskaThat is how "intrusion detection system"  work, but for that we have remote port mirroring 14:46
mtomaskano vswitch port will not be exposed in api14:47
mtomaskaIt would just create an interface directly in OVS (maybe using an agent)14:47
sean-k-mooneyok so i miss understood what -local-mirror-port and --port are14:47
mtomaskaDisregard example :) See comment#214:48
sean-k-mooneyack14:49
sean-k-mooneyignore me then14:49
lajoskatonado we need perhaps spec to make clear all these questions for everybody?14:49
mtomaskaBut yes what would happen under the hood is something like this. ovs-vsctl add-port br-int destination_port -- set interface destination_port type=internal14:49
mtomaskabut if we have ovs-tcpdump then I am questioning value of this RFE :) 14:50
haleybmtomaska: that was going to be my next question - is it basically doing what ovs-tcpdump does?14:50
sean-k-mooneydid they ever fix teh performance impact of mirroring form a vhost-user prot to type=internal14:50
mtomaskaI need to experiment with ovs-tcpdump14:51
sean-k-mooneyall tx traffinc to a type internal port used to fall back to the ovs-vswichd main thread14:51
* haleyb shrugs14:51
sean-k-mooneywell tx and rx14:51
mtomaskaYep there is performance impact for sure, thats why this is for debug only14:51
sean-k-mooneythat used to significally impact the performace of the PMDs14:51
mlavalleyeah, I think that at this point in time experimnting with ovs-tcpdump seems that the sensible next step14:51
mtomaskaI agree14:52
lajoskatona+114:52
mtomaskaso maybe this RFE is incomplete 14:52
mlavallethat way we can decide if the RFE is needed14:52
haleybmtomaska: yes, see if it does what you need and we can go from there14:53
mtomaskait is not for me personally :) 14:53
mtomaskabut end customers. But yes, let me work on it bit more14:54
mlavalleoh, you don't do this for fun?14:54
mtomaskaand I can bring it up next week14:54
ralonsohmtomaska, thanks!14:54
mtomaskayes I like to mirror packets to my TV and watch in evenings14:54
lajoskatonathanks14:54
haleybmtomaska: like the matrix14:54
ralonsohin any case, a document about using ovs-tcpdump would be also a good output14:54
mtomaskathank you for the input14:55
slaweqmtomaska that's weird hobby :P14:55
mtomaskaACK14:55
haleybok, we are about out of time, are there any other topics to discuss?14:56
mtomaskaralonsoh: I have a doc already maybe I just need to make it public14:56
mlavallenot from me14:56
mtomaskaall from me14:56
lajoskatonanothing from me14:56
haleybok, thanks for attending everyone and have a nice weekend!14:56
haleyb#endmeeting14:56
opendevmeetMeeting ended Fri Jan  9 14:56:57 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_drivers/2026/neutron_drivers.2026-01-09-14.01.html14:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2026/neutron_drivers.2026-01-09-14.01.txt14:56
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_drivers/2026/neutron_drivers.2026-01-09-14.01.log.html14:56
mlavalle\o14:57
ralonsohbye!14:57
slaweqhave a nice one and see you14:57
slaweqo/14:57
mtomaskao/14:57
lajoskatonao/14:57
opendevreviewBodo Petermann proposed openstack/os-vif master: Fixed bridge name when per_port_bridge is used  https://review.opendev.org/c/openstack/os-vif/+/96641015:15
sean-k-mooneyralonsoh: does https://paste.opendev.org/show/bMep54CV84Hrrhm5kWxp/ looks familar to you? devstack for me is failing with that15:52
ralonsohsean-k-mooney, yes, one sec15:54
ralonsohis that stable/2025.1?15:54
sean-k-mooneyim also seeing error related ot ovn hashrigns in perodics15:54
sean-k-mooneynot sure if that is related15:55
ralonsohyes, it could be15:55
ralonsohsean-k-mooney, what version is that?15:55
sean-k-mooneysqlalchemy.exc.ProgrammingError: (pymysql.err.ProgrammingError) (1146, "Table 'neutron.ovn_hash_ring' doesn't exist")15:55
sean-k-mooneymaster15:55
sean-k-mooneyon debian 1315:55
sean-k-mooneyspecifically 644d2b767df84e46a4df6b1b8f8725452dcda79615:56
sean-k-mooneythis is the vm i started setting up yesterday15:56
ralonsohsean-k-mooney, what do you have in mechanism_drivers?15:57
ralonsohin the ml2_plugin.ini file15:57
sean-k-mooneyhttps://paste.opendev.org/show/blassOEdIr28ZeSG96T0/15:57
sean-k-mooneyi dont have any neutron related optio ndefien din my local.conf15:58
sean-k-mooneybut ill check15:58
sean-k-mooney[ml2]15:59
sean-k-mooneytenant_network_types = geneve15:59
sean-k-mooneyextension_drivers = port_security,qos15:59
sean-k-mooneytype_drivers = local,flat,vlan,geneve15:59
sean-k-mooneyoverlay_ip_version = 415:59
sean-k-mooneymechanism_drivers = ovn15:59
sean-k-mooneyso that all look normal15:59
ralonsohand the ranges? because this error means you don't have enough tags (vlan, vxlan, geneve)16:00
ralonsohis that error happening during the boot?16:00
ralonsohor any specific command?16:00
sean-k-mooneythe error is preventign devstack form completing16:01
ralonsohwell, this is while creating a network16:01
sean-k-mooneybut ya the ranges seam to be broken16:01
sean-k-mooneyactully no16:01
ralonsohyeah, most probably during the public network creation16:01
sean-k-mooneyvlan is broken16:01
ralonsohcan you pass me the whole ml2_plugin file?16:02
ralonsohin private16:02
sean-k-mooneyhttps://paste.opendev.org/show/bUGtHnI7Xesy8bniqQVW/16:02
sean-k-mooneysure one sec16:02
sean-k-mooneyhttps://termbin.com/iin2d16:02
sean-k-mooneythe public network shoudl be of type flat16:03
sean-k-mooneyand then the tenatn network shoudl be geneve16:03
sean-k-mooneyby deault in openstack any way16:03
sean-k-mooneys/openstack/devstack/16:03
ralonsohyes, I see nothing wrong there16:03
sean-k-mooneythere is not rant defiend for vlan network which will break but we shoudl not be useing htem by default16:04
ralonsohin not range defined, that means you can use all vlan tags16:05
sean-k-mooneyoh really didnt know htat16:05
sean-k-mooneyhttps://termbin.com/e8sb that is my actul devstack log16:06
sean-k-mooneyoh no its truncated16:06
sean-k-mooneyhttps://paste.opendev.org/show/boTzCM8kagCRi2I6b5mU/16:07
sean-k-mooneythat waqs the reported error16:07
sean-k-mooneyso its creating the private network16:07
sean-k-mooneywhich shoudl be geneve16:07
ralonsohsean-k-mooney, ok maybe there could be a race condition (maybe)16:09
ralonsohthere is one single API initializing the segment ranges16:09
ralonsohand because of this:16:10
ralonsoh[ml2_type_geneve]16:10
ralonsohvni_ranges = 1:6553616:10
ralonsohyou are creating 65K registers16:10
ralonsohtry reducing that to 1:100016:10
opendevreviewMerged openstack/neutron master: Cleanup stale DHCP ports not bound to host  https://review.opendev.org/c/openstack/neutron/+/96877016:10
sean-k-mooneyok but im just using the defaults so im not sure why this woudl have broken.16:11
sean-k-mooneyselect count(*) from  ml2_geneve_allocations; return 016:11
ralonsohso that's a problem16:12
sean-k-mooneyya i wonder if its related to the other db issue whre teh tabel was not found16:12
ykarelsean-k-mooney, i recall seeing that but when did multiple stack.sh and some improper cleanup16:13
ykarelyou seen in clean/first stack.sh?16:14
ralonsohsean-k-mooney, can I have access to this VM?16:14
sean-k-mooneyykarel: i ran clan and stacked again before i hit this16:14
sean-k-mooneyralonsoh: sure i shoudl be able to give you access16:15
ykarelif not it could be same issue, and unstack.sh ; stack.sh should help. also recently came to attention there is some issue with unstack, so if you see process running even after unstack.sh then thats another issue16:15
ralonsohI wasn't aware of this, good to know16:15
ykarelin that case have to manually clean those process or reboot until that's fixed16:15
sean-k-mooneyykarel: ya so unstack and stack shoudl be enough without clean16:15
sean-k-mooneyif you need to clean there is a bug in neutron or devstack16:15
ykarelsean-k-mooney, i mean bug with unstack16:16
ykarelso after unstack if you see neutron process running then thats the bug i am referring, recently gthiemon1e mentioned about it16:16
sean-k-mooneyso i havent checked if ther are any neutron process left after an unstack but i can do that seperatly.16:16
sean-k-mooneyykarel: that could be a regrssion with the split out of q-svc into neutron-api ectra16:17
ykarelyeap16:17
sean-k-mooneyralonsoh: do you have ipv6? if not i can set up a port forwad for you but if you like i can try replicating this on my other vm first and let you knwo if its repoducable16:17
ralonsohsean-k-mooney, no, my internet provider gives me only ipv416:18
sean-k-mooneyack ill need to do a prot forward then or maybe tmate16:19
ralonsohsean-k-mooney, once you stopped everything and stack again, check the ml2_geneve_allocations;16:19
sean-k-mooneylet me kick of the same install on the other vm whihc is clean first and see if it repoduces16:19
sean-k-mooneyis neutron testign with py 3.13 and or debian 13 by the way just ruling out that that is the issue16:21
ykarelatleast that not seen with ci jobs running with ovn and python3.13 so high chance not related to that16:24
ykareli think fresh vm shouldn't see it but let's see16:24
sean-k-mooneyack i was debating replciating this on noble i can trivally create vms with that instead.16:24
sean-k-mooneyi will let ye know if it repoduces16:25
sean-k-mooneyif it does not ill unstack and see what if any service are left behind on the broken node16:25
ykarel+116:25
opendevreviewRodolfo Alonso proposed openstack/neutron master: WIP == Detach the stdout and stderr after killing a external process  https://review.opendev.org/c/openstack/neutron/+/97253816:38
sean-k-mooneyralonsoh: while that is running https://review.opendev.org/c/openstack/os-vif/+/966410 fixes a bug with the per-port-bridge option which is the experimental temporty workaround16:45
ralonsohsean-k-mooney, let me review that patch now16:45
sean-k-mooneyno rush just mentioning it since ist realted ot the live migration topic16:45
ralonsohsean-k-mooney, right, we call  `_create_vif_port` with bridge in this case, that is pbXXX16:48
ralonsohwe should not use always vif.network.bridge but L20816:49
sean-k-mooneyright so the problem is the port exist check16:52
sean-k-mooneyalways used vif.network.bride16:52
ralonsohin general, and checking the FT test, I think the patch is correct16:53
sean-k-mooneyso we were missign the logic from https://review.opendev.org/c/openstack/os-vif/+/966410/4/vif_plug_ovs/ovs.py#20816:53
sean-k-mooneyto take the per port overried when needed16:54
sean-k-mooneythe bug is kind of sbutle https://bugs.launchpad.net/os-vif/+bug/213322516:55
sean-k-mooneyit all work fine once.16:55
sean-k-mooneyi dont think we are currently testign with per_port_bridge in ci but even if we were we dont do agent restarts in ci16:55
sean-k-mooneythey added coverage for thsi in teh functional test explcitly16:56
sean-k-mooneyhttps://review.opendev.org/c/openstack/os-vif/+/966410/4/vif_plug_ovs/tests/functional/test_plugin.py#22416:56
sean-k-mooneyby calling plug again16:56
ralonsohthat should be idemponent, right?16:57
sean-k-mooneyyep16:57
sean-k-mooneybecuase the exist check was using teh wrong bride it was assuming that this was the first time the prot was added16:57
sean-k-mooneywhich ment we tried to creat the qos porfile again in the ovsdb16:57
sean-k-mooneyon one hand its a valid thing to backport on the other hand im not sure that folks really use that config option in production16:59
sean-k-mooneyas you are aware that was my intiall attempt to fix the live migration downtime before ovn supprot multipel logical switch ports17:01
sean-k-mooneyhttps://github.com/openstack/os-vif/commit/b837c1a74f37191692a820711e431a75516a4abf17:01
ralonsohyes, I remember that17:01
sean-k-mooneyi never removed the experimatl part when we reaisied it wold not install the flows without the chase table entry17:02
ralonsohI'll push on monday morning an update of the os_vif_tap_creation patch17:02
ralonsohjust only for vanilla ovs and marked for removal17:02
sean-k-mooneyack.17:04
opendevreviewBrian Haley proposed openstack/neutron-lib master: Use py313 for all neutron-lib jobs  https://review.opendev.org/c/openstack/neutron-lib/+/97273517:21
sean-k-mooneyralonsoh: ykarel  so ya unstacking is not stopping any fo the neutron- devstack services https://termbin.com/vs1f18:05
sean-k-mooneyso that is a bug in devstack18:06
ralonsohq- and neutron- should be the same18:06
sean-k-mooneyclean works but that should not be required18:06
ralonsohI'll check that on Monday and I'll open a bug18:06
sean-k-mooneywell apprently not any more18:06
ralonsohsorry, I'm disconnecting now, is quite late for me18:07
ralonsohsee you!!18:07
sean-k-mooneyhttps://github.com/openstack/devstack/blob/master/unstack.sh#L161-L164 shoudl have cleaned it up18:07
sean-k-mooneyand now worries o/18:07
sean-k-mooney*no worries18:07
sean-k-mooneyi need to dig more but i think the issue is the neutron-* service are never populated in the ENABLED_SERVICES dict18:27
sean-k-mooneythe bug is here https://github.com/openstack/devstack/blob/master/lib/neutron#L609-L65018:46
sean-k-mooneywe are enabling the service in start_neutron_service_and_check18:46
sean-k-mooneyi.e. addign them to the enabeld service dict18:46
sean-k-mooneythat is incorrect that function wont be run in the unstack path18:46
opendevreviewJakub Libosvar proposed openstack/neutron master: func: Remove MySQL test case from OVN base class  https://review.opendev.org/c/openstack/neutron/+/97147218:47
opendevreviewJakub Libosvar proposed openstack/neutron master: func: Generate SQL file with schema  https://review.opendev.org/c/openstack/neutron/+/97296118:47
sean-k-mooneyso we need to factor out the extnetion of the ENABLED_SERVICES dict into a seperate function that is involed in both code paths so we have the same list18:47
sean-k-mooneyin general we shoudl minims calling enable_service in devstack itself although there are some valid cases but where we do call it we have to ensure its decupled form the logic ot actilly start the service18:49
sean-k-mooneyralonsoh: https://review.opendev.org/c/openstack/devstack/+/972963 fixes unstack but i need to confirm i didnt break stacking19:07
sean-k-mooneyok stakcing works and with that change applied to clean up the stales service when i unstacked 19:55
opendevreviewMerged openstack/networking-bgpvpn master: Change test code to use project_id key  https://review.opendev.org/c/openstack/networking-bgpvpn/+/97222620:51
opendevreviewBrian Haley proposed openstack/neutron master: Change agent and Ipam code to use project_id  https://review.opendev.org/c/openstack/neutron/+/97258922:31
opendevreviewBrian Haley proposed openstack/neutron master: Use project_id key in port plugin code  https://review.opendev.org/c/openstack/neutron/+/97298222:31
opendevreviewJakub Libosvar proposed openstack/neutron master: func: Do not teardown DB if not dirty  https://review.opendev.org/c/openstack/neutron/+/97298523:41
opendevreviewJakub Libosvar proposed openstack/neutron master: DNM: Trigger functional tests  https://review.opendev.org/c/openstack/neutron/+/97298623:51

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