| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2026-07-10 | |||
| 09:09:48 | gibi | yeah just because we have attachment_id it does not tell us if the compute finished attaching the volume to the VM | |
| 09:10:01 | gibi | the versioned notification is better in this regard as that is sent from the compute side | |
| 09:10:02 | sean-k-mooney | if i recall the oder correctly , the volume gets attached in cinder, then we udate the bdms and finally attach it to the vm | |
| 09:10:07 | sean-k-mooney | the last 2 might be reversed | |
| 09:10:07 | gibi | yepp | |
| 09:10:36 | sean-k-mooney | so the way to do this reliabley todya is server show and look at the attachments there | |
| 09:10:39 | gibi | the attachment_id is added to the BDM by the conductor before the compute attaches the volume to the instance | |
| 09:10:56 | sean-k-mooney | ack ok then i did remember the order | |
| 09:58:56 | opendevreview | Balazs Gibizer proposed openstack/nova master: Do not try to return empty attachment_id from API https://review.opendev.org/c/openstack/nova/+/996757 | |
| 09:58:56 | opendevreview | Balazs Gibizer proposed openstack/nova master: Reproducer for https://bugs.launchpad.net/nova/+bug/2160224 https://review.opendev.org/c/openstack/nova/+/996756 | |
| 10:02:19 | gibi | sean-k-mooney: gmaan: ^^ this might help dicussing the situation further | |
| 10:06:21 | sean-k-mooney | gibi: woudl you agree that the bug shoudl be set to low an asgined to you give your working on it and respocen schema validation is not only off by defualt but docuemnted as never to be used in production only for testing? | |
| 11:02:56 | gibi | sean-k-mooney: sure | |
| 11:04:47 | gibi | I'm filing a separate bug to switch response schema validation errors to HTTP500 with a clear error message | |
| 11:07:42 | sean-k-mooney | ack just an fyi ill be finishing up in the next 2 hours so i will be unlike to be around when gmaan comes onlien but i sumemrised my toughts in the bug | |
| 11:07:52 | gibi | https://bugs.launchpad.net/nova/+bug/2160303 | |
| 11:08:01 | gibi | sean-k-mooney: no worries | |
| 11:08:09 | gibi | and thanks for the response in the bug | |
| 11:09:43 | sean-k-mooney | in terems of the 404 responce it might evenually make sesen to only return the attahcment if the atttachment is fully compelte form a nova point of view but that out of scope fo the current bugs you filed | |
| 11:10:23 | sean-k-mooney | well or have a better way | |
| 11:10:30 | sean-k-mooney | to knwo if the attach is done | |
| 11:10:44 | gibi | yeah | |
| 11:10:45 | sean-k-mooney | which is actully tracked seperatly | |
| 11:11:17 | sean-k-mooney | https://bugs.launchpad.net/nova/+bug/2058928 and or hte spec rajesh started | |
| 11:11:44 | sean-k-mooney | ultimplate you shoudl be able to pool the intatnce actin event for completion | |
| 11:13:15 | sean-k-mooney | gibi: switching topics for a sec im going to see if i can quickly update the futureist patches to adress your feedback and split the fix and feature | |
| 11:13:34 | sean-k-mooney | gibi: do you want to proceed with the quick workaround in nova in the interim? | |
| 11:14:27 | gibi | sean-k-mooney: we can wait with the hack in nova as that is top of the functional test with threading series anyhow | |
| 11:14:54 | sean-k-mooney | well i was going to suggest rebasign to master | |
| 11:15:03 | sean-k-mooney | if we didnt want to wait to save some ci time | |
| 11:15:55 | sean-k-mooney | but ok ill see if i can get the actual fix tidied up quickly | |
| 13:14:32 | opendevreview | Balazs Gibizer proposed openstack/nova master: Check service_ref before destroy https://review.opendev.org/c/openstack/nova/+/996793 | |
| 13:14:32 | opendevreview | Balazs Gibizer proposed openstack/nova master: HACK:Speed up functional test in threading mode https://review.opendev.org/c/openstack/nova/+/996500 | |
| 14:10:38 | opendevreview | Merged openstack/placement master: tests: Support file-backed SQLite URL in placement fixtures https://review.opendev.org/c/openstack/placement/+/993106 | |
| 14:21:20 | sean-k-mooney | gibi: sorry i just didnt get as far with the futurist work as i hoped for today. im going to wrap up shortly but ill take a look at it again on monday | |
| 14:21:55 | gibi | sean-k-mooney: no worries. Have a nice weekend | |
| 14:23:44 | sean-k-mooney | i might push what i have before i leave i need to pack a bag and trun on the ac in my car to cool it down or ill melt when i get into it | |
| 14:24:27 | sean-k-mooney | i plugged it in to charge ealer and the temperture in the car was 35c which is what i get for parking it facing uphil and south on a nice day | |
| 14:27:42 | sean-k-mooney | oh i was under estermating it say its at 44c right now. i am happy it also has a remote ac feature | |
| 15:32:48 | opendevreview | Mike Lowe proposed openstack/nova master: Fix PCI cleanup when a move claim is aborted https://review.opendev.org/c/openstack/nova/+/996822 | |
| 17:57:15 | opendevreview | Merged openstack/nova master: tests: use file-backed Placement SQLite in functional threading https://review.opendev.org/c/openstack/nova/+/992581 | |
| 19:47:29 | gmaan | gibi: sean-k-mooney[m] stuck on other things downstream but I will check and reply on bug/gerrit. most probably today otherwise Monday | |
| #openstack-nova - 2026-07-11 | |||
| 01:51:11 | opendevreview | Takashi Kajinami proposed openstack/nova master: libvirt: Validate valid cache mode at config input layer https://review.opendev.org/c/openstack/nova/+/933327 | |
| 01:51:11 | opendevreview | Takashi Kajinami proposed openstack/nova master: libvirt: Use native DictOpt for disk_cachemode https://review.opendev.org/c/openstack/nova/+/915390 | |
| 01:52:34 | opendevreview | Takashi Kajinami proposed openstack/nova master: Remove unused default argument https://review.opendev.org/c/openstack/nova/+/922073 | |
| 10:25:05 | opendevreview | Takashi Kajinami proposed openstack/nova master: Remove unused default argument https://review.opendev.org/c/openstack/nova/+/922073 | |
| 13:21:41 | opendevreview | Takashi Kajinami proposed openstack/nova stable/2026.1: Return 400 for invalid properties for locked memory https://review.opendev.org/c/openstack/nova/+/996878 | |
| 15:20:42 | opendevreview | Takashi Kajinami proposed openstack/nova master: doc: Update cursive repository path https://review.opendev.org/c/openstack/nova/+/996880 | |
| 16:07:10 | opendevreview | Takashi Kajinami proposed openstack/nova master: Remove tempest-pg-full https://review.opendev.org/c/openstack/nova/+/996887 | |
| 17:12:50 | opendevreview | Takashi Kajinami proposed openstack/placement master: tox: Use constraints option https://review.opendev.org/c/openstack/placement/+/996893 | |
| #openstack-nova - 2026-07-13 | |||
| 03:19:05 | opendevreview | yaguang proposed openstack/nova master: libvirt: enable Hyper-V evmcs on Intel VMX hosts https://review.opendev.org/c/openstack/nova/+/995620 | |
| 06:37:02 | opendevreview | Bhavana proposed openstack/nova master: Add Minimal Displacement Solver for MIG GPU Repartitioning https://review.opendev.org/c/openstack/nova/+/996058 | |
| 06:42:09 | opendevreview | Bhavana proposed openstack/nova master: Add Minimal Displacement Solver for MIG GPU Repartitioning https://review.opendev.org/c/openstack/nova/+/996058 | |
| 08:16:03 | gibi | sean-k-mooney[m] gmaan: I think we need to tweak the functional-py313-threading job as it pulls placement from pypi but we needed to land a fix in placement master that is not release yet. | |
| 08:16:24 | gibi | https://zuul.opendev.org/t/openstack/build/fdefa3b20f4f471cb6f0ef9b29ccd241/log/job-output.txt#870 | |
| 08:18:05 | sean-k-mooney[m] | We can use tox siblings and required projects I think to pull master | |
| 08:18:17 | sean-k-mooney[m] | Or we can just release placement | |
| 08:24:27 | gibi | I assuem that zuul's required-projects only work with devstack based jobs not tox based ones | |
| 08:24:30 | bauzas | gibi: good call | |
| 08:24:39 | gibi | I'm trying to find an example of tox siblings | |
| 08:24:41 | bauzas | we can do a placement release indeed | |
| 08:24:50 | bauzas | that looks to me the simpliest | |
| 08:24:59 | gibi | can we release from master randomly even if placement is expected to be release at milestones? | |
| 08:25:06 | gibi | elodilles: ^^ cc | |
| 08:25:18 | bauzas | gibi: we can do a rc2 | |
| 08:25:28 | bauzas | lemme check the release cycle | |
| 08:25:40 | gibi | we are not in an rc period | |
| 08:25:45 | bauzas | we can do milestones | |
| 08:25:47 | gibi | M2 is in a week or se | |
| 08:25:50 | gibi | so | |
| 08:25:54 | bauzas | oh sorry, I meant milestone-2 | |
| 08:26:03 | gibi | can we do an M2 early/ | |
| 08:26:05 | gibi | ? | |
| 08:26:07 | bauzas | yes | |
| 08:26:13 | bauzas | or any milestone | |
| 08:26:14 | bauzas | sec | |
| 08:26:40 | bauzas | https://releases.openstack.org/reference/release_models.html#cycle-with-rc | |
| 08:26:43 | gibi | OK, if we can that is indeed the cheapest | |
| 08:27:00 | bauzas | "The “cycle-with-rc” model describes projects that produce a single release at the end of the cycle, with one or more release candidates (RC) close to the end of the cycle and optional development milestone betas published on a per-project need." | |
| 08:27:22 | bauzas | we can create any optional milestone release if we wantr | |
| 08:27:25 | gibi | ^^ that means to me that we need to push an rc1 now | |
| 08:27:45 | bauzas | no | |
| 08:27:48 | gibi | that description does not talk about milestone releaes | |
| 08:27:52 | bauzas | we will need to publish a rc1 | |
| 08:27:53 | elodilles | gibi: yes we can release a 16.0.0.0b1 or 0b2 release anytime | |
| 08:27:56 | gibi | OK | |
| 08:27:57 | bauzas | that ^ | |
| 08:28:01 | gibi | I will propose a b1 now | |
| 08:28:05 | gibi | thanks | |
| 08:28:36 | bauzas | we have to create a RC1 at least, yes | |
| 08:28:44 | elodilles | not many project do that, but some do release beta releases (milestone releases) | |
| 08:29:03 | elodilles | just merged a couple of neutron related beta release patches in the morning ;) | |
| 08:29:03 | bauzas | but as elodilles said, we can create *any* milestone releases | |
| 08:29:18 | bauzas | we did created m1, m2 and m3 before :) | |
| 08:29:28 | bauzas | like 10 years before | |
| 08:29:35 | gibi | yeah but not in the last couple of years | |
| 08:29:51 | gibi | but it seems the release tooling correctly chose b1 if I ask for a hibiscus milestone release | |
| 08:29:56 | gibi | so all seems good | |
| 08:30:19 | elodilles | :] | |
| 08:30:38 | bauzas | lovely | |