Earlier  
Posted Nick Remark
#openstack-nova - 2026-09-28
16:47:06 gibi I retract that
16:47:07 gmaan GA is this week right
16:47:10 gibi yeah
16:47:13 gibi but I retract
16:47:21 gibi I already approved the py314 change for nova on master
16:47:28 gmaan k
16:47:29 gibi so I should not block this eitehr
16:47:30 gibi :)
16:47:38 gibi sorry I'm all over the place a bit
16:47:55 gibi I stop now but I will check back on those changes tomorrow
16:48:07 gmaan sure, take rest
16:48:11 gibi o/
18:37:09 opendevreview Merged openstack/nova master: Move upper python version job https://review.opendev.org/c/openstack/nova/+/1007299
18:56:38 dansmith gmaan: got the master one
20:42:16 gmaan dansmith: thanks
20:57:10 opendevreview Merged openstack/nova master: Call volume detach rollback API if detach fails https://review.opendev.org/c/openstack/nova/+/880399
20:57:23 opendevreview Merged openstack/nova master: Fix ironic instance rebuild with API >=2.93 https://review.opendev.org/c/openstack/nova/+/963298
20:57:35 opendevreview Merged openstack/nova master: Update graceful shutdown known issue to list resize case also https://review.opendev.org/c/openstack/nova/+/1006095
23:05:30 tkajinam gmaan, in case you are still around, do you mind adding +A to https://review.opendev.org/c/openstack/placement/+/1007283 ?
#openstack-nova - 2026-09-29
01:27:10 opendevreview Merged openstack/nova master: Check volume status before live migration https://review.opendev.org/c/openstack/nova/+/973750
01:40:17 gmaan tkajinam: done
03:17:53 opendevreview Merged openstack/placement master: Move upper python version job https://review.opendev.org/c/openstack/placement/+/1007283
08:28:20 opendevreview Juan Larriba proposed openstack/nova master: Add OpenTelemetry tracing middleware for Nova https://review.opendev.org/c/openstack/nova/+/982871
08:31:51 bauzas gibi: Uggla: I'm looking at https://docs.openstack.org/reno/latest/user/usage.html based on our discussions
08:35:19 bauzas gibi: Uggla: I actually misunderstood one bit, https://review.opendev.org/c/openstack/nova/+/1003386 is included in rc1
08:35:43 gibi that is a different patch
08:35:55 gibi https://review.opendev.org/c/openstack/nova/+/1006095
08:36:01 gibi this is the one we discussed
08:36:16 gibi landed on master yesterday
08:36:30 gibi https://review.opendev.org/c/openstack/nova/+/1007329 backport to stable/hibiscus is open
08:36:52 bauzas yeah but 1006095 updartes the reno file from 1003386 IIUC
08:37:13 bauzas given 1003386 merged before rc1, it should be included in https://docs.openstack.org/releasenotes/nova/2026.2.html#rc1
08:37:22 bauzas but I don't see it
08:37:32 bauzas (hence my confusion)
08:38:33 bauzas elodilles: do you have an idea why https://review.opendev.org/c/openstack/nova/+/1003386 isn't showing up in https://docs.openstack.org/releasenotes/nova/2026.2.html#rc1 ?
08:39:24 bauzas https://zuul.opendev.org/t/openstack/build/674c7dcf33ba437eac0781bc264b18af shows me it was promoted post-merge
08:41:43 bauzas I think I found the bug
08:41:44 bauzas https://docs.openstack.org/nova/latest/contributor/releasenotes.html
08:42:01 bauzas known_issues is probably a section name we didn't configured
08:42:16 bauzas gibi: Uggla: ^
08:45:22 bauzas I mean, the whole section won't never be documented even in master until we fix the issue
08:54:54 gibi ❯ grep known_issue -R releasenotes
08:54:55 gibi releasenotes/notes/nova-graceful-shutdown-task-tracking-13485c8346512ae4.yaml:known_issues:
08:55:08 gibi this is our only known_issues note in the whole repo
08:55:21 gibi so probably it is better to fix the note on master and update the backport patch
08:56:14 bauzas yeah, I'm currently working on a fix
08:56:27 bauzas probably s/known_issues/issues but I'm doublechecking the right section name
08:57:04 bauzas I don't see where we configured the sections like reno mentions in https://docs.openstack.org/reno/latest/user/usage.html#configuring-reno
08:59:10 gibi the template does not offer known_issues section at all
08:59:48 gibi ❯ reno new foo
08:59:48 gibi no configuration file in: ./releasenotes/config.yaml, ./reno.yaml
08:59:48 gibi Created new notes file in releasenotes/notes/foo-4968025a44dda86d.yaml
08:59:48 gibi ❯ vim releasenotes/notes/foo-4968025a44dda86d.yaml
08:59:48 gibi ❯ grep issue releasenotes/notes/foo-4968025a44dda86d.yaml
08:59:50 gibi issues: List known issues here, or remove this section. All of the list items in
09:00:45 gibi we have no specific reno config in the repo as far as I see
09:00:47 bauzas yeah this is why I documented https://docs.openstack.org/nova/latest/contributor/releasenotes.html years before
09:01:07 bauzas lemme write a patch using issues and we'll see
09:01:19 gibi we have releasenotes/source/conf.py but not config.yaml
09:01:49 gibi bauzas: OK
09:02:37 bauzas I'll run the tox target on my laptop to check the doc
09:10:00 bauzas mmm, I don't see the section even after changing the section name :(
09:10:10 bauzas lemme push the patch and we'll see
09:10:45 opendevreview Sylvain Bauza proposed openstack/nova master: Fix graceful shutdown release note section https://review.opendev.org/c/openstack/nova/+/1007837
09:12:11 gibi thanks
09:13:25 opendevreview Sylvain Bauza proposed openstack/nova master: Fix graceful shutdown release note section https://review.opendev.org/c/openstack/nova/+/1007837
09:16:25 bauzas hmmmm
09:16:37 bauzas really weird, still doesn't show up
09:16:50 bauzas but I'm pretty sure that issues is the default name
09:16:57 elodilles i don't know the reason either :/
09:18:13 elodilles the docs page refreshes like hourly, but i guess this is not the reason here
09:18:34 bauzas I'm not seeing it even on my laptop as generated page
09:19:09 bauzas maybe because the original commit was using a wrong section name ?
09:21:44 gibi yeah worth trying a new note file
09:21:51 gibi to see if that works or not
09:22:06 bauzas this is exactly what I'm testing :)
09:22:54 bauzas bingo
09:22:57 opendevreview Sylvain Bauza proposed openstack/nova master: DNM: Test issues https://review.opendev.org/c/openstack/nova/+/1007839
09:23:42 bauzas we're stuck
09:24:05 bauzas basically because of the original section name, the relnote is not appearing
09:24:13 bauzas and I +2d that patch, f...
09:24:38 bauzas NEVER TRUST MY FYCKING BRAIN
09:30:48 bauzas hmmm, https://docs.openstack.org/reno/latest/releasenotes/index.html#relnotes-3-4-0 reno shouldn't have accepted the original YAML then
09:34:04 bauzas https://zuul.opendev.org/t/openstack/build/5648bd0f571e4304a63d2f39e1371283 used reno-4.1.0 so we should have failed it
09:37:40 bauzas OK, I think I understand the problem
09:38:31 bauzas we shipped the original file pre-rc1, which means we have the same commit on both master and 2026.2 branches but we're trying to update its master only
09:39:31 bauzas I honestly don't know how to fix that
09:40:59 bauzas stephenfin: tkajinam: you're unfortunately the last contributors of reno, so I probably need your help here :)
09:42:12 bauzas context : we had an original reno commit using a wrong section name that was merged before RC1, and now we want to fix it, but this isn't possible as the original commit is now branched (ie. https://review.opendev.org/c/openstack/nova/+/1007837/2 doesn't show up in the relnotes)
09:42:46 bauzas I guess we will need to backport that patch to 2026.2 which will automatically heal once we merge the two patches in tree, right?
09:43:04 bauzas I can try on my local git repo
09:49:49 bauzas gibi: Uggla: elodilles: OK, I get it, we need to merge some backport of https://review.opendev.org/c/openstack/nova/+/1007837 in 2026.2 before we tag 34.0.0
09:50:28 bauzas I remembered reno using git tags
09:51:31 opendevreview Sylvain Bauza proposed openstack/nova stable/2026.2: Fix graceful shutdown release note section https://review.opendev.org/c/openstack/nova/+/1007840
09:59:50 opendevreview Balazs Gibizer proposed openstack/nova master: Func test for cross cell resize with PCI source failure https://review.opendev.org/c/openstack/nova/+/1007841
10:32:12 opendevreview Kamil Sambor proposed openstack/nova master: Replace StaticallyDelayingWrapper with futurist DelayingExecutor https://review.opendev.org/c/openstack/nova/+/997410
11:25:58 stephenfin bauzas: iirc you shouldn't need to backport https://review.opendev.org/c/openstack/nova/+/1007837. reno will use the initial commit to determine what version to map to, but it should take the contents from the latest version of the file
11:34:28 bauzas stephenfin: but how to fix the issue ?
11:34:46 bauzas stephenfin: as you see the CI job doesn't create a right release note
11:58:36 stephenfin Sorry, lunch. I'd have expected https://review.opendev.org/c/openstack/nova/+/1007837 to fix it without the need for the backport but the CI result for that is pretty clear that it doesn't do so. I'm not sure why reno isn't picking that up 😕

Earlier   Later