| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2026-04-15 | |||
| 19:53:34 | melwitt | cc gibi ^ | |
| 20:49:29 | opendevreview | ribaudr proposed openstack/nova master: Reproduce bug #2132147: AZ not reverted after failed live migration https://review.opendev.org/c/openstack/nova/+/984874 | |
| 20:49:30 | opendevreview | ribaudr proposed openstack/nova master: Fix instance AZ not reverted after failed live migration https://review.opendev.org/c/openstack/nova/+/984875 | |
| 21:01:38 | Uggla | Thanks bauzas. I'm aware of your constraints this Wednesday, so I've picked subjects you're comfortable with to ensure you can catch up quickly. I hope that helps! | |
| 23:40:51 | opendevreview | Merged openstack/nova stable/2024.2: Reproducer for bug 2114951 https://review.opendev.org/c/openstack/nova/+/959525 | |
| #openstack-nova - 2026-04-16 | |||
| 00:07:21 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: adjust requirement checks for mem_encryption guests https://review.opendev.org/c/openstack/nova/+/967974 | |
| 00:07:21 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: address minor issues pointed out in the review https://review.opendev.org/c/openstack/nova/+/983278 | |
| 00:07:22 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: introduce a check between mem_encryption and locked_memory https://review.opendev.org/c/openstack/nova/+/971300 | |
| 00:48:02 | opendevreview | Merged openstack/nova stable/2024.2: Fix bug 2114951 https://review.opendev.org/c/openstack/nova/+/959526 | |
| 05:49:33 | opendevreview | Esra Ozkan proposed openstack/nova master: Check volume status before live migration https://review.opendev.org/c/openstack/nova/+/973750 | |
| 06:39:21 | gibi | melwitt: re DB: thanks. I will dig forward to understand how we approach parallelism regarding DB interactions. dansmith had valid questions about the problem we see in the func test env (the transaction within transaction issue) if it affects production code as well or not. | |
| 06:40:11 | gibi | melwitt: re vtpm job: Yeah reducing parallelism in the job make sense to me. Unfortunately the patch faild the vtpm job now with a live migration failure, so we still have something fishy there | |
| 06:42:35 | gibi | I rechecked it to see if it is an intermittent network issue between the host during live migration or something deeper | |
| 06:48:06 | opendevreview | ChungWon Lee proposed openstack/nova master: Add regression test for bug #2088066 https://review.opendev.org/c/openstack/nova/+/984900 | |
| 06:49:58 | opendevreview | Balazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal https://review.opendev.org/c/openstack/nova/+/960130 | |
| 06:52:34 | opendevreview | Balazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal https://review.opendev.org/c/openstack/nova/+/960130 | |
| 06:55:07 | gibi | melwitt: dansmith: re DB parallelism: in parallel (sic) with my manual tracing I try to trigger the transaction within transaction issue in devstack with mysql in my rally fake virt job https://review.opendev.org/c/openstack/nova/+/960130 that has a lot bigger concurrency on conductor operations that the rest of our jobs due to having many (fake virt) computes and may VM boots in parallel. | |
| 06:55:49 | gibi | last time I run that rally the conductor had no native thrading support but we can have result now with native conductor | |
| 07:13:00 | opendevreview | Kamil Sambor proposed openstack/nova master: Enable threading mode for proxy services https://review.opendev.org/c/openstack/nova/+/976089 | |
| 07:45:03 | opendevreview | ChungWon Lee proposed openstack/nova master: Add regression test for bug #2088066 https://review.opendev.org/c/openstack/nova/+/984900 | |
| 07:57:04 | opendevreview | Kamil Sambor proposed openstack/nova master: Test nova CLI commands with native threading https://review.opendev.org/c/openstack/nova/+/984036 | |
| 09:31:43 | opendevreview | ChungWon Lee proposed openstack/nova master: Add regression test for bug #2088066 https://review.opendev.org/c/openstack/nova/+/984900 | |
| 10:26:48 | opendevreview | Ashish Gupta proposed openstack/nova master: Run functional test with threading mode https://review.opendev.org/c/openstack/nova/+/979850 | |
| 10:26:48 | opendevreview | Ashish Gupta proposed openstack/nova master: Add native threading support to functional test (DB, RPC, test case ID) https://review.opendev.org/c/openstack/nova/+/980179 | |
| 11:14:20 | opendevreview | Kamil Sambor proposed openstack/nova master: Enable threading mode for proxy services https://review.opendev.org/c/openstack/nova/+/976089 | |
| 11:17:33 | r-taketn | gibi: bauzas: Hello. Could you please check the remaining two sev refactor patches again? https://review.opendev.org/q/topic:%22bp/generalize-sev-code%22 | |
| 11:17:41 | bauzas | I'll today | |
| 11:18:07 | r-taketn | bauzas: Thank you | |
| 11:18:20 | r-taketn | Regarding the last patch, I've set it to WIP. I've also added it as an PTG item. I'd like to discuss the approach/direction. | |
| 11:20:53 | gibi | r-taketn: looks good to me | |
| 11:23:19 | r-taketn | gibi: Thank you for your quick review. | |
| 11:43:47 | opendevreview | Stephen Finucane proposed openstack/nova master: tox: Remove override of install_command https://review.opendev.org/c/openstack/nova/+/984918 | |
| 11:46:00 | stephenfin | gibi: sean-k-mooney: bauzas: Need to wait on CI, but I'd appreciate if we could get ^ in sooner rather than later. You can't currently run any tox commands in nova if tox-uv is installed (which is that case for me since I installed the python3-tox-uv package) | |
| 11:46:50 | stephenfin | Coincidentally, tox-uv brings a nice little speed increase during package installation, particularly for things like nova with lots of dependencies | |
| 12:00:27 | sean-k-mooney | i have one comment in the commit message that ill push shortly | |
| 12:00:33 | sean-k-mooney | just testign your patch locally | |
| 12:20:41 | gibi | melwitt: dansmith: with native threadig in conductor I does not see any threadpooling for DB. There are 64 RPC threads and couple of other threads, for RPC hearthbeat, cotyledon management, oslo looping call, and our own executor pools. If I configure all our pool to the smallest possible then the list of threads are easy to review https://paste.openstack.org/show/bmpzWGa9YXAjYF4SXxHS/ non of them | |
| 12:20:47 | gibi | seems to be DB related. I will check this with eventlet as well | |
| 12:23:31 | gibi | but I more or less assume that the DB transaction is running in the GreenThread that is used to receive the RPC request | |
| 12:24:31 | gibi | sean-k-mooney: if you wondering why I'm writing the above then: dansmith asked the question if our overlapping transaction issue we see in the functional test effects the production code as well or not. | |
| 12:25:01 | opendevreview | Bartosz Bezak proposed openstack/nova stable/2025.2: fix: device_by_alias should respect config type https://review.opendev.org/c/openstack/nova/+/984920 | |
| 12:25:15 | opendevreview | Bartosz Bezak proposed openstack/nova stable/2025.1: fix: device_by_alias should respect config type https://review.opendev.org/c/openstack/nova/+/984921 | |
| 12:28:17 | sean-k-mooney | gibi: so my understandign is there are mutlipel driver impleaiton in sqlachmey for mariadb | |
| 12:28:30 | sean-k-mooney | and not all fo them use a conenction pool inthe same way | |
| 12:28:47 | sean-k-mooney | so i dont know if that is expected or now with how devstack deploy by defualt | |
| 12:29:16 | sean-k-mooney | gibi: maybe zeeck? can say quickly if we ping them | |
| 12:30:07 | sean-k-mooney | but ya i dont know if that affect productio or not either we would have to dige deeper | |
| 12:31:25 | gibi | I think connection pool and worker pool is different. We can have N connection object and not have any extra worker threads that doing the transaction with those connection objects | |
| 12:32:22 | gibi | I printed the pool of the DB engine before we use QueuePool there in devstack for native threading. I can print it for eventlet too | |
| 12:44:49 | gibi | yepp in eventlet mode it we also use a QueuePool for DB connectons | |
| 12:44:54 | sean-k-mooney | right so conenction pooling shoudl jsut eb reusing tcp conntion not nessiarly requirign sperate threads | |
| 12:45:21 | gibi | yepp | |
| 12:45:24 | gibi | that is what I see | |
| 12:45:52 | sean-k-mooney | yep i think that is the upsteam sqlachemy behvior for mysql | |
| 12:46:09 | sean-k-mooney | so i dont think this is a regression in behvior | |
| 12:46:21 | gibi | so when an RPC GreenThread executes a long transaction it either yields and then other GreenThreads can also start another transaction. Or it does not yield and then the no other RPC can run | |
| 12:46:29 | sean-k-mooney | but when we use in memroy dbs with sqlight i think we are suign the NULLPOOL | |
| 12:46:57 | gibi | yes, in functest we have some static pooling because the in memory DB needs a single connection to keep the DB aliave | |
| 12:47:21 | gibi | so maybe the overlapping transaction happens across that single static connection | |
| 12:47:47 | gibi | OK that is something I can try to trace | |
| 12:48:53 | gibi | if there is one static connection for the in memory DB then that can be the point of the race. And I imagine that it is very different from the DB perspective if one connection starts a transaction within a transaction or two independent connection runs two independent but timewise overlapping transactions | |
| 12:49:49 | gibi | dansmith: ^^ | |
| 12:54:49 | gibi | sqlalchemy.pool.impl.StaticPool this is the pool in the functional test by default | |
| 12:55:43 | gibi | https://github.com/sqlalchemy/sqlalchemy/blob/7dce9fec9d2071351d0c003a607955eca5dcf9ae/lib/sqlalchemy/pool/impl.py#L451 | |
| 12:57:39 | sean-k-mooney | isnt that why oslo.db is overreidng | |
| 13:05:21 | gibi | when the SQLite DB is in memory then we use StaticPool when we switch to file based (for the api DB) then that file based DB uses sqlalchemy.pool.impl.NullPool | |
| 13:05:43 | gibi | this also points to that maybe the source of the race is the StaticPool | |
| 13:06:20 | gibi | null pool basically always opens a new connection | |
| 13:06:23 | gibi | so it cannot race | |
| 13:06:53 | gibi | I'm not sure what oslo_db overrides in this regards | |
| 13:13:19 | bauzas | stephenfin: silly question but I was thinking we were still supporting tox 2.x, am I wrong ? | |
| 13:15:06 | bauzas | hmmm, OK, we were supporting 3.18 | |
| 13:15:45 | stephenfin | bauzas: I assume you mean tox 3.x (2.x hasn't seen a release in nearly a decade). In any case, no. The only reason to have kept tox 3.x around was for Python 2.x support but that's not been an issue for some time | |
| 13:16:34 | stephenfin | That and tempest, which is relying on the shared venv thing that doesn't work in tox 4.x (I've been working on fixing that in the background) but this doesn't affect nova itself | |
| 13:19:28 | gibi | so I do see that with StaticPool we can basically checkout the same connection twice without returning the connection first. So two parallel entity can talk to the same tcp connection object. I guess in eventlet mode in the functional test our yield points was in places where such cross talk did not cause two transaction to overlap inside that single connection. And in production code we don't use | |
| 13:19:34 | gibi | the StaticPool so we never checkout the same tcp connection twice so crosstalk cannot happen < dansmith my current answer to your question | |
| 13:19:46 | bauzas | stephenfin: yeah sorry, typo there, I meant 3.x | |
| 13:19:47 | opendevreview | Takashi Kajinami proposed openstack/os-vif master: Bump min version of pyroute2 https://review.opendev.org/c/openstack/os-vif/+/984934 | |
| 13:20:22 | bauzas | stephenfin: but there is a CLI behavioural change with posargs when upgrading to 4.x, which is pretty impactful for our community, I'd appreciate more than just a file change | |
| 13:21:17 | gibi | (and I have proof that this code is magic. it contains fairys: sqlalchemy.pool.base._ConnectionFairy) | |
| 13:22:34 | gibi | we cannot switch to the null pool with in memory SQLite as the DB is freed as soon as the connection drops and nullpool drops it after use | |
| 13:23:32 | gibi | we cannot really use QueuePool either as two connection cannot address the same in memory SQLite, that will be two different in memory DB for the two connection | |
| 13:24:11 | gibi | so either we use StaticPool with one single never closed connection or we switch away from in memory DB | |
| 13:24:35 | gibi | the former is racy in threading mode when two threads checks out the same connection object and crosstalk | |
| 13:31:21 | stephenfin | bauzas: a CLI change? | |
| 13:34:49 | bauzas | stephenfin: https://tox.wiki/en/4.6.4/upgrading.html isn't quite a short doc | |
| 13:35:18 | bauzas | and my main concern is https://github.com/tox-dev/tox/issues/2183 | |
| 13:38:22 | bauzas | s/ |
|
| 13:38:50 | opendevreview | Kamil Sambor proposed openstack/nova master: Test nova CLI commands with native threading https://review.opendev.org/c/openstack/nova/+/984036 | |
| 13:41:38 | sean-k-mooney | bauzas: we are already likely using 4.28.0 | |
| 13:41:47 | sean-k-mooney | we dont cap tox via upper-constraits | |
| 13:41:53 | bauzas | if you just pip install tox, sure | |
| 13:42:01 | sean-k-mooney | right which is what we do | |
| 13:42:02 | bauzas | like myself | |
| 13:42:30 | dansmith | sean-k-mooney: who is we? :) I don't pip install tox, I brew install it | |
| 13:42:40 | sean-k-mooney | im talkign about the ci jobs | |
| 13:43:07 | dansmith | gibi: sounds like this was an interesting diversion but that led to some understanding about why we're hitting this in tests only and that production should be good yeah? | |
| 13:43:14 | sean-k-mooney | and as i noted in the reivew tox installs a seperve version of tox in a venv and uses htat if the min veriosn is above our current one | |
| 13:43:50 | sean-k-mooney | s/our current one/ the one that is locally installed/ | |
| 13:44:06 | bauzas | I'm doublechecking but I'm almost sure we have somewhere in our docs that says we should use tox 3.x | |