| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-12-09 | |||
| 12:27:28 | sean-k-mooney | this should be poplulated before we ever get to _build_and_run_instance | |
| 12:29:36 | noonedeadpunk | unless class is not re-inited at some point.... | |
| 12:36:28 | opendevreview | Dominik proposed openstack/nova master: Regression test for Placement allocations remaining during failed schedule https://review.opendev.org/c/openstack/nova/+/969251 | |
| 12:36:50 | opendevreview | Dominik proposed openstack/nova master: Remove Placement allocations in the broken build cleanup https://review.opendev.org/c/openstack/nova/+/968446 | |
| 12:38:36 | DominikDanelski[m] | sean-k-mooney: All right, I added a comment explaining why the exact flavour doesn't matter, so now all discussion is resolved. | |
| 12:39:33 | noonedeadpunk | sean-k-mooney: so I reverted 78be1679312768383b684fa70ca4d2f5c4e35fa9 and instance become spawning normally :( | |
| 12:40:16 | noonedeadpunk | will submit a bug report in the meanwhile I guess | |
| 12:40:38 | sean-k-mooney | an do they have allcoation against the placemetn RPs for the gpu usage? | |
| 12:41:00 | sean-k-mooney | i..e there were no other sideffects? | |
| 12:41:21 | sean-k-mooney | im wondering if we are misisng a fix for one of the ohter caching bugs related to OTU devices | |
| 12:41:28 | sean-k-mooney | in the sable branch | |
| 12:41:45 | sean-k-mooney | gibi and dan were fixing some other bugs around the same time | |
| 12:44:10 | noonedeadpunk | it looks fine? https://paste.openstack.org/show/bj8ZZgxzHSYHZF2hGFvg/ | |
| 12:45:00 | noonedeadpunk | hm, maybe I am missing some backport... | |
| 12:45:47 | noonedeadpunk | nah, I think we're on current HEAD of 2025.1 | |
| 12:47:37 | sean-k-mooney | ya that looks correct to me too | |
| 13:00:02 | noonedeadpunk | created report https://bugs.launchpad.net/nova/+bug/2134469 | |
| 13:21:04 | DominikDanelski[m] | sean-k-mooney: Sorry, then do I understand correctly what you wrote at 12:55 that if I replied to the comment but made no code changes, just as I did now, you wouldn't be informed about it? | |
| 13:31:35 | DominikDanelski[m] | I wouldn't want to constantly bug you here, but then I don't know to best reach you when I reply. | |
| 13:50:47 | sean-k-mooney | DominikDanelski[m]: so every unless you adjust it in you settings if your on a review (reviewwr or cc) you will get an email every time somone comments or pushes a new patch | |
| 13:51:32 | sean-k-mooney | DominikDanelski[m]: and it show up with your name rater then zuul in the from | |
| 13:51:42 | sean-k-mooney | i.e. Dominik (Code Review) | |
| 13:51:58 | sean-k-mooney | so i will be notifed by ether a comment or a new aptchset | |
| 13:52:18 | sean-k-mooney | i just might not see it for a while depending on how often i check my email | |
| 15:26:04 | nicolairuckel | I'm a bit lost trying to figure out which code gets called for a cold migration. There is the `_cold_migrate` function in manager.py but I kind of expected a call to the driver at some point where I could copy the NVRAM but I can't find anything like that. Am I overlooking something or am I on the wrong track to begin with? | |
| 15:48:14 | tkajinam | nicolairuckel, check migrate_disk_and_power_off in LibvirtDriver | |
| 15:48:30 | tkajinam | I think nova internally calls resize method | |
| 17:15:01 | nicolairuckel | tkajinam: Hm, that's what I tried first but it didn't work. I'm going to check it again. Maybe I did something wrong when I was testing it. Thank you. | |
| 18:03:12 | opendevreview | Nicolai Ruckel proposed openstack/nova master: Preserve UEFI NVRAM variable store https://review.opendev.org/c/openstack/nova/+/959682 | |
| 18:04:31 | nicolairuckel | I pushed my attempt so maybe someone else sees anything that is obviously wrong there. | |
| 18:56:50 | nicolairuckel | This is what I tried: https://review.opendev.org/c/openstack/nova/+/959682/comment/2c08400d_baac062c/ | |
| 19:31:32 | opendevreview | Zhan Zhang proposed openstack/nova-specs master: Refine network setup procedure in live migrations https://review.opendev.org/c/openstack/nova-specs/+/970298 | |
| 19:35:52 | Zhan[m] | sean-k-mooney: As we previously discussed I've submitted the spec for https://bugs.launchpad.net/nova/+bug/2128665, unfortunately didn't make it for 2026.1 so this will be in 2026.2. | |
| 19:42:49 | opendevreview | Zhan Zhang proposed openstack/nova-specs master: Refine network setup procedure in live migrations https://review.opendev.org/c/openstack/nova-specs/+/970298 | |
| 19:54:16 | opendevreview | Zhan Zhang proposed openstack/nova-specs master: Refine network setup procedure in live migrations https://review.opendev.org/c/openstack/nova-specs/+/970298 | |
| #openstack-nova - 2025-12-10 | |||
| 03:07:46 | opendevreview | yangjianfeng proposed openstack/nova master: Fix missing allocations due to unsuccessful evacuations https://review.opendev.org/c/openstack/nova/+/970335 | |
| 05:10:42 | opendevreview | ChungWon Lee proposed openstack/nova master: Fix error when multiple security group in a project with same name https://review.opendev.org/c/openstack/nova/+/970337 | |
| 05:15:20 | opendevreview | Rajesh Tailor proposed openstack/nova master: Add functional reproducer for bug 2096884 https://review.opendev.org/c/openstack/nova/+/970238 | |
| 05:46:40 | opendevreview | ChungWon Lee proposed openstack/nova master: Fix error when multiple security group in a project with same name https://review.opendev.org/c/openstack/nova/+/970337 | |
| 08:02:59 | cw0306-lee[m] | Hi, nova team!... (full message at <https://matrix.org/oftc/media/v1/media/download/ATEBK2ecPfYUpbLTNfvf7ZZI5ImOneLHiJwCBCzpzpfS8rYqhQHpXqp3Yg5cVsWTSml0Rob0cV8Er3o0OIgJL7RCebT2H1TAAG1hdHJpeC5vcmcvVEJRdG5zdmxzcHBvRElxTWhxYndZdFRT>) | |
| 09:06:43 | opendevreview | Rajesh Tailor proposed openstack/nova master: Clean up volume attachments when server create fails https://review.opendev.org/c/openstack/nova/+/970350 | |
| 10:00:51 | opendevreview | Rajesh Tailor proposed openstack/nova master: Clean up volume attachments when server create fails https://review.opendev.org/c/openstack/nova/+/970350 | |
| 13:16:20 | opendevreview | Rajesh Tailor proposed openstack/nova master: Clean up volume attachments when server create fails https://review.opendev.org/c/openstack/nova/+/970350 | |
| 14:33:39 | sean-k-mooney | ratailor: melwitt ^ https://review.opendev.org/c/openstack/nova/+/970350 looks like a a duplciate or related to work started by DominikDanelski[m] on https://bugs.launchpad.net/nova/+bug/2132020 in https://review.opendev.org/c/openstack/nova/+/969251/6 and https://review.opendev.org/c/openstack/nova/+/968446/3 | |
| 14:35:48 | sean-k-mooney | ratailor: melwitt the quta exceed part of https://bugs.launchpad.net/nova/+bug/2096884 is likely a sideeffect of the fact we do nto delete the allcoation when the server errors out as reported in https://bugs.launchpad.net/nova/+bug/2132020 | |
| 17:14:12 | JayF | https://review.opendev.org/c/openstack/nova/+/969833 is proposed for stable/2024.2, +2'd already by Elod, V+1, ready to merge. Please help me land it? | |
| 17:17:39 | sean-k-mooney | sure | |
| 17:18:37 | sean-k-mooney | JayF: done | |
| 17:18:46 | JayF | thank you | |
| 17:18:57 | JayF | now to wonder into the unmaintained wastes to land it further :P | |
| 17:20:00 | sean-k-mooney | i intentially do not have merge rights there so this is as far as i cna help but i think elod still does and we dont enforce mutliple +2 there so once this is merge they can probly hlep with older branches | |
| 17:20:13 | JayF | I am unmaintained core as well :D | |
| 17:20:24 | JayF | I put the link (https://review.opendev.org/c/openstack/nova/+/970448) for 2024.1 in #openstack-unmaintained | |
| 18:10:41 | noonedeadpunk | sooo... about https://review.opendev.org/c/openstack/nova-specs/+/900296/13/specs/2026.1/approved/cross-az-instance-scheduling.rst | |
| 18:11:01 | noonedeadpunk | just to be clear - should I be adding 409 to catch AZ conflict or not? | |
| 18:11:38 | noonedeadpunk | and also - I'm not sure about this one - does nova allows a VM to be a member of multiple server groups? | |
| 18:56:05 | opendevreview | Merged openstack/nova stable/2024.2: [ironic] Ensure unprovision happens for new states https://review.opendev.org/c/openstack/nova/+/969833 | |
| #openstack-nova - 2025-12-11 | |||
| 06:42:50 | opendevreview | yangjianfeng proposed openstack/nova master: Fix missing allocations due to unsuccessful evacuations https://review.opendev.org/c/openstack/nova/+/970335 | |
| 07:21:07 | opendevreview | huanhongda proposed openstack/nova master: live migration: Complete cleanup if post_live_migration fails https://review.opendev.org/c/openstack/nova/+/967652 | |
| 10:32:25 | opendevreview | yangjianfeng proposed openstack/nova master: [WIP] Fix: resources leak due to failed live-migration https://review.opendev.org/c/openstack/nova/+/970597 | |
| 13:11:20 | noonedeadpunk | hey folks! I've started looking into multi-cell docs (https://docs.openstack.org/nova/latest/admin/cells.html) and got kind of confused by sepr conductor part. Or specifically - how to tell it that it's a superconductor? | |
| 13:11:44 | noonedeadpunk | As, I can imagine, conductor is able to fetch cells connection details from the api database | |
| 13:11:56 | noonedeadpunk | but then how to tell a cell conductor not to do that? | |
| 13:12:43 | noonedeadpunk | and that it should operate only with own database, and never reach api database? Just don't define api_database section? | |
| 13:13:01 | noonedeadpunk | And also - does it make sense to do superconductor setup at all? | |
| 13:13:30 | noonedeadpunk | As in RHOSP 16 docs I've seen that still it has limit of 500 hosts across all cells... | |
| 13:13:45 | noonedeadpunk | (which I'd guess is due to network limit, but not sure) | |
| 13:48:51 | noonedeadpunk | so my guess is that super conductor just has an [api_database] section, while regular conductors only [database] | |
| 14:59:03 | opendevreview | Julien LE JEUNE proposed openstack/nova stable/2024.2: Fix bug 2000069 https://review.opendev.org/c/openstack/nova/+/970634 | |
| 15:26:09 | dansmith | noonedeadpunk: if you have multiple cells, you need a superconductor, or at least delegate one cell's conductors to be the superconductor function | |
| 15:28:09 | sean-k-mooney | noonedeadpunk: dont read teh RHOSP docs for anythign related to cells, if you do it will cuase you pain and confustion | |
| 15:28:26 | sean-k-mooney | noonedeadpunk: tripelo did not impelent cells well | |
| 15:28:54 | sean-k-mooney | the 500 limit in 16 was just that was what it was tested too | |
| 15:29:04 | sean-k-mooney | there is no actullly limit at 500 computes in nova | |
| 15:29:17 | sean-k-mooney | tripleo however had scaling issuees with 500+ servers | |
| 15:29:42 | dansmith | also that ^ :) | |
| 15:30:02 | sean-k-mooney | that was related to how it used heat and the heat -> ansible -> puppet workflow tripleo used | |
| 15:32:36 | noonedeadpunk | dansmith: but how you actually do that? | |
| 15:32:45 | noonedeadpunk | as I have not found option or any config reference | |
| 15:32:49 | dansmith | noonedeadpunk: do what? | |
| 15:33:02 | noonedeadpunk | do say that this conductor is a superconductor | |
| 15:33:15 | dansmith | noonedeadpunk: having an api_database is critical, but the superconductor is the conductor that your API nodes talk to over MQ, | |
| 15:33:37 | dansmith | so the [transport] of the API,scheduler, etc defines which conductors operate as the superconductor | |
| 15:33:42 | sean-k-mooney | each conductor uses a sepeate rabbtit clsuter or at least the rabbit vhost. the supper conductor is pointing at the cell0 rabbit cluster and has api access | |
| 15:34:08 | noonedeadpunk | I guess I'm kind of missing property to do so | |
| 15:34:39 | noonedeadpunk | I'd be assuming that superconductor get's connection details from the api_database? | |
| 15:34:43 | sean-k-mooney | the api db access enabeld the super conductor to conenct to the other rabbit message buess dbs for the other cells if needed to cordiate cross cell migration ectra | |
| 15:34:58 | sean-k-mooney | yep the cell mappign table | |
| 15:35:12 | noonedeadpunk | but like - what if you add api_database connection to all cell conductors? | |
| 15:35:34 | noonedeadpunk | but then they will also be configured to use own cell db/mq | |
| 15:35:38 | sean-k-mooney | that wont break anything | |
| 15:35:56 | sean-k-mooney | the importnat thing is that each cell has its own rabbit or rabbit vhost | |
| 15:35:57 | noonedeadpunk | so kinda this way all cell conductors are "superconductor"? | |
| 15:36:19 | sean-k-mooney | so the condutors and compute for a given cell use a specific rabbit | |
| 15:36:28 | dansmith | I guess sean-k-mooney wants to answer this, so I guess I'll back off | |
| 15:36:46 | sean-k-mooney | no go ahaed if you like | |
| 15:37:16 | noonedeadpunk | eventually osa also lacks proper multicell, despite some our users have it | |
| 15:37:20 | sean-k-mooney | i just wated to give a higelevel over view i tough i had a good link but i am not finding it in my history | |
| 15:37:46 | noonedeadpunk | so I wanted to implement it, but I fail to get to the bottom of how everything is connected, and I did not found any super relevant options in nova.conf reference | |
| 15:38:02 | noonedeadpunk | https://docs.openstack.org/nova/latest/admin/cells.html ? | |