Wednesday, 2026-02-18

elodilleshi Oslo team, just a heads up that oslo.middleware release might have a valid cross job error: https://review.opendev.org/c/openstack/requirements/+/97714511:23
frickler2026-02-17 17:38:07.940492 | ubuntu-noble | 2026-02-17 17:38:07,125 WARNING [oslo_middleware.cors] Allowed origin [http://valid.example.com] already exists, skipping11:49
fricklerthis is generated right next to https://review.opendev.org/c/openstack/oslo.middleware/+/970631/1/oslo_middleware/cors.py which makes it very suspicous. see also the discussion between stephenfin and tkajinam there11:49
fricklerhmm ... looks like this is actually nova's fault and it should return a list here? https://opendev.org/openstack/nova/src/branch/master/nova/tests/functional/test_middleware.py#L39 but that would also be an indication that adding the error would have been a good idea after all11:55
opendevreviewTakashi Kajinami proposed openstack/oslo.rootwrap master: Refactor test_KillFilter  https://review.opendev.org/c/openstack/oslo.rootwrap/+/97711612:38
opendevreviewTakashi Kajinami proposed openstack/oslo.rootwrap master: Find cat command externally  https://review.opendev.org/c/openstack/oslo.rootwrap/+/97713012:39
tkajinamelodilles, frickler checking12:59
tkajinamlet me propose a fix but this is actually caused by internal hack to override the option.13:02
elodillesthanks tkajinam for working on this, too! o/13:03
tkajinamfrickler, maybe, though as long as the appropriate config load mechanism is used the value should be converted to a list13:11
tkajinamthe hack there directly injects the final value there which has been outdated. I guess the warning has been shown for some time (though I don't know why I didn't notice that earlier when I did mass deprecation cleanup stuff13:12
tkajinamdamani[m], do you have a minute to review https://review.opendev.org/c/openstack/oslo.utils/+/975115 ?13:15
tkajinamelodilles, https://review.opendev.org/c/openstack/nova/+/977217 will be merged soon and may unblock the bump. just fyi13:47
elodillestkajinam: awesome \o/ thanks!13:52
ralonsohgmaan, hberaud[m] haleyb: https://bugs.launchpad.net/neutron/+bug/2141304 is still broken14:34
ralonsohand now we have a release with this issue14:34
ralonsohhttps://bugs.launchpad.net/neutron/+bug/214212214:35
gmaanralonsoh: I tested the neutron neutron-ovs-tempest-with-oslo-master and it passed on the fix15:33
ralonsohgmaan, yes, its passing but one of the service is not15:35
ralonsohAt least one of the workers, I'm still investigating that15:35
ralonsohin any case, we still have this nasty warning message15:36
ralonsohhttps://paste.opendev.org/show/b63UDQh8c5dHcDI5OFxJ/15:36
ralonsohis that necessary?15:37
gmaanralonsoh: do you have review link also where it is failing or job link to see config etc15:44
ralonsohyes, one sec. It is happening in ovn agent and nova scheduler15:44
ralonsohhttps://zuul.opendev.org/t/openstack/build/2f8feee00a3e4bf286e879ee03274d77/log/controller/logs/screen-q-ovn-agent.txt#30515:45
ralonsohhttps://zuul.opendev.org/t/openstack/build/2f8feee00a3e4bf286e879ee03274d77/log/controller/logs/screen-n-sch.txt#2515:45
gmaanralonsoh: ohk. different jobs15:48
ralonsohgmaan, I think we need to revert the requirements patch to bump oslo.service for now15:53
gmaanralonsoh: about warning, yes by default oslo.service try for spawn method and raise warning if service is not spawnable15:57
gmaanralonsoh: let me check the bug and if I can fix15:58
opendevreviewMerged openstack/tooz master: Deprecate etcd driver  https://review.opendev.org/c/openstack/tooz/+/97683816:00
opendevreviewMerged openstack/tooz master: Deprecate Consul driver  https://review.opendev.org/c/openstack/tooz/+/94773316:00
gmaanralonsoh: they are just warning and logging exception right? they are not stopping worker to start16:05
ralonsohgmaan, yes, just logging16:07
ralonsohsorry, I need to leave now, I'll connect later today16:07
gmaanralonsoh: ohk, i got confused with 'is still broken'16:07
ralonsohgmaan, well, the periodics job is16:08
ralonsohit seems to be related to a specific periodic worker16:08
gmaanralonsoh: k, can you link me the one failing16:08
ralonsohI'm still investigating16:08
ralonsohhttps://bugs.launchpad.net/oslo.service/+bug/214212216:08
gmaanthanks16:08
gmaanwhich job is this exactly, job name16:09
gmaanit seems it is telling to fallback to fork but cotyledon trying with spawn and fail16:13
haleybi'll try and find the job he was looking at, but from what i can tell neutron-periodic-workers is only true in our grenade jobs16:16
haleybgmaan: for example, if you look at this simple change https://review.opendev.org/c/openstack/neutron/+/976822 and go into the logs for the neutron-ovn-grenade-multinode job that log file is there with the pickle failures16:19
gmaanhaleyb: ack, thanks16:21
gmaanhaleyb: yeah, i think that is only log, i checked but I was asking the one failing16:22
haleybi don't know what change that was from16:24
gmaanso if I understood. neutron gate is ok with oslo.service 4.5.0 but one periodic job failing16:25
haleybit's a periodic worker in the job16:28
haleybhttps://review.opendev.org/c/openstack/neutron/+/92211016:29
gmaanyeah, so that works fine as it fall back to 'fork' and only log warnings with traceback. but does not fail right? or periodic worker does not cause job to fail and they does not start silently 16:30
haleybit's no longer eventlet16:30
gmaanI can disable the warning traceback as that is confusing in logs16:30
haleybfrom the log i think it fails to run, so i think things like quotas could be impacted16:32
gmaani see16:33
haleybwe'd have to find a previous log to see i guess16:35
haleybfrom that same change, but on a previous PS with the older oslo.service this is the log, https://998fb44128151542469d-eb0bc8c584c4b7f1435696f4fd53c9a4.ssl.cf2.rackcdn.com/openstack/083c92e432844601ac012d64da34283e/controller/logs/screen-neutron-periodic-workers.txt16:37
opendevreviewGhanshyam Maan proposed openstack/oslo.service master: Improve warning and more logging  https://review.opendev.org/c/openstack/oslo.service/+/97724116:46
gmaanhaleyb: ralonsoh : disabling that log traceback and adding more logs to see what's going on for neutron case , testing neutron with this https://review.opendev.org/c/openstack/neutron/+/97724216:53
haleybgmaan: ack, thanks!16:53
opendevreviewGhanshyam Maan proposed openstack/oslo.service master: Improve warning and more logging  https://review.opendev.org/c/openstack/oslo.service/+/97724117:20
sean-k-mooneyhas there been any work to remove eventlet form teh default deps in oslo service and oslo messaging and only install it via extras?18:19
sean-k-mooneyim asking becasue it woudl be nice to be able to not pull them in for services that are not using them18:20
gmaanralonsoh: if you have your DNM testing change for debugging, please use this so that it will give less warning and more logs about multiprocessing context. https://review.opendev.org/c/openstack/oslo.service/+/97724118:31
gmaanI am going to debug the same but do not know where exactly things failed because neutron grenade multinode job did not fail.18:31
sean-k-mooneyoslo log by defualt is callent eventlutils form oslo utiels https://github.com/openstack/oslo.log/blob/d0f0bf3ee5d5676b99b4ad7656089808c2aeb35b/oslo_log/log.py#L303C5-L341 that does a tryimport of eventlet https://github.com/openstack/oslo.utils/blob/master/oslo_utils/eventletutils.py#L42 which indirectly import greeenlet adn apprelntly that can cause segfault on python 3.1318:42
sean-k-mooneyin some cases at least in unit tests18:42
sean-k-mooneyhum this might eb an issue with sqligt19:07
sean-k-mooneyits unfortunate that oslo log is uncondtionally causes oslo.utils to try and import eventlet and greenlet even if its not monkey patching19:07
gmaanhaleyb: ralonsoh: with my debugging change, I can see oslo.service selected the 'spawn' method because it did not find any pickle issue in service worker but later in multiprocessing it fail for the pickle issue - https://zuul.opendev.org/t/openstack/build/2b9a15586d6745dfb70b718b26b75e3f/log/controller/logs/screen-neutron-periodic-workers.txt#4027 21:12
gmaanhaleyb: one question, I could not find this error in latest run of neutron-ovn-grenade-multinode in https://review.opendev.org/c/openstack/neutron/+/976822 where i can find the error in its previous run21:13
gmaanis it not 100% failing or it depends on the other runtime things21:14
haleybgmaan: it might not be 100%, i don't see it in that change but others seem to have it21:52
gmaanhaleyb: yeah, I think I am finding the issue here, maybe it is with the conf object pickle which is done by multiprocessing but not by oslo.service21:52
gmaanthat is the difference I can see how multiprocessing check picklable and fail which oslo.serviec does not21:53
gmaanthis one, it has the conf object into process_obj and it fail when it test the picklable https://github.com/python/cpython/blob/0bbdb4e897ae909af39cd93f7a25de89b724ab47/Lib/multiprocessing/popen_spawn_posix.py#L4721:55
gmaanfail here https://github.com/python/cpython/blob/0bbdb4e897ae909af39cd93f7a25de89b724ab47/Lib/multiprocessing/reduction.py#L6021:55
gmaanneed to go for lunch, after that I will push the fix and recheck on neutron testing change21:56
haleybsure, thanks, maybe rodolfo will be back by then21:57
opendevreviewGhanshyam Maan proposed openstack/oslo.service master: Threading mode: check conf object picklable before 'spawn'  https://review.opendev.org/c/openstack/oslo.service/+/97724123:00

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