| opendevreview | Merged openstack/nova master: Check volume status before live migration https://review.opendev.org/c/openstack/nova/+/973750 | 01:27 |
|---|---|---|
| gmaan | tkajinam: done | 01:40 |
| opendevreview | Merged openstack/placement master: Move upper python version job https://review.opendev.org/c/openstack/placement/+/1007283 | 03:17 |
| opendevreview | Juan Larriba proposed openstack/nova master: Add OpenTelemetry tracing middleware for Nova https://review.opendev.org/c/openstack/nova/+/982871 | 08:28 |
| bauzas | gibi: Uggla: I'm looking at https://docs.openstack.org/reno/latest/user/usage.html based on our discussions | 08:31 |
| bauzas | gibi: Uggla: I actually misunderstood one bit, https://review.opendev.org/c/openstack/nova/+/1003386 is included in rc1 | 08:35 |
| gibi | that is a different patch | 08:35 |
| gibi | https://review.opendev.org/c/openstack/nova/+/1006095 | 08:35 |
| gibi | this is the one we discussed | 08:36 |
| gibi | landed on master yesterday | 08:36 |
| gibi | https://review.opendev.org/c/openstack/nova/+/1007329 backport to stable/hibiscus is open | 08:36 |
| bauzas | yeah but 1006095 updartes the reno file from 1003386 IIUC | 08:36 |
| bauzas | given 1003386 merged before rc1, it should be included in https://docs.openstack.org/releasenotes/nova/2026.2.html#rc1 | 08:37 |
| bauzas | but I don't see it | 08:37 |
| bauzas | (hence my confusion) | 08:37 |
| 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:38 |
| bauzas | https://zuul.opendev.org/t/openstack/build/674c7dcf33ba437eac0781bc264b18af shows me it was promoted post-merge | 08:39 |
| bauzas | I think I found the bug | 08:41 |
| bauzas | https://docs.openstack.org/nova/latest/contributor/releasenotes.html | 08:41 |
| bauzas | known_issues is probably a section name we didn't configured | 08:42 |
| bauzas | gibi: Uggla: ^ | 08:42 |
| bauzas | I mean, the whole section won't never be documented even in master until we fix the issue | 08:45 |
| * bauzas double-checks where we configured (I mean, this was myself for nova) reno in our repo | 08:45 | |
| gibi | ❯ grep known_issue -R releasenotes | 08:54 |
| gibi | releasenotes/notes/nova-graceful-shutdown-task-tracking-13485c8346512ae4.yaml:known_issues: | 08:54 |
| gibi | this is our only known_issues note in the whole repo | 08:55 |
| gibi | so probably it is better to fix the note on master and update the backport patch | 08:55 |
| bauzas | yeah, I'm currently working on a fix | 08:56 |
| bauzas | probably s/known_issues/issues but I'm doublechecking the right section name | 08:56 |
| 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:57 |
| gibi | the template does not offer known_issues section at all | 08:59 |
| gibi | ❯ reno new foo | 08:59 |
| gibi | no configuration file in: ./releasenotes/config.yaml, ./reno.yaml | 08:59 |
| gibi | Created new notes file in releasenotes/notes/foo-4968025a44dda86d.yaml | 08:59 |
| gibi | ❯ vim releasenotes/notes/foo-4968025a44dda86d.yaml | 08:59 |
| gibi | ❯ grep issue releasenotes/notes/foo-4968025a44dda86d.yaml | 08:59 |
| gibi | issues: List known issues here, or remove this section. All of the list items in | 08:59 |
| gibi | we have no specific reno config in the repo as far as I see | 09:00 |
| bauzas | yeah this is why I documented https://docs.openstack.org/nova/latest/contributor/releasenotes.html years before | 09:00 |
| bauzas | lemme write a patch using issues and we'll see | 09:01 |
| gibi | we have releasenotes/source/conf.py but not config.yaml | 09:01 |
| gibi | bauzas: OK | 09:01 |
| bauzas | I'll run the tox target on my laptop to check the doc | 09:02 |
| bauzas | mmm, I don't see the section even after changing the section name :( | 09:10 |
| bauzas | lemme push the patch and we'll see | 09:10 |
| opendevreview | Sylvain Bauza proposed openstack/nova master: Fix graceful shutdown release note section https://review.opendev.org/c/openstack/nova/+/1007837 | 09:10 |
| gibi | thanks | 09:12 |
| opendevreview | Sylvain Bauza proposed openstack/nova master: Fix graceful shutdown release note section https://review.opendev.org/c/openstack/nova/+/1007837 | 09:13 |
| bauzas | hmmmm | 09:16 |
| bauzas | really weird, still doesn't show up | 09:16 |
| bauzas | but I'm pretty sure that issues is the default name | 09:16 |
| elodilles | i don't know the reason either :/ | 09:16 |
| elodilles | the docs page refreshes like hourly, but i guess this is not the reason here | 09:18 |
| bauzas | I'm not seeing it even on my laptop as generated page | 09:18 |
| bauzas | maybe because the original commit was using a wrong section name ? | 09:19 |
| gibi | yeah worth trying a new note file | 09:21 |
| gibi | to see if that works or not | 09:21 |
| bauzas | this is exactly what I'm testing :) | 09:22 |
| bauzas | bingo | 09:22 |
| opendevreview | Sylvain Bauza proposed openstack/nova master: DNM: Test issues https://review.opendev.org/c/openstack/nova/+/1007839 | 09:22 |
| bauzas | we're stuck | 09:23 |
| bauzas | basically because of the original section name, the relnote is not appearing | 09:24 |
| bauzas | and I +2d that patch, f... | 09:24 |
| bauzas | NEVER TRUST MY FYCKING BRAIN | 09:24 |
| 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:30 |
| bauzas | https://zuul.opendev.org/t/openstack/build/5648bd0f571e4304a63d2f39e1371283 used reno-4.1.0 so we should have failed it | 09:34 |
| bauzas | OK, I think I understand the problem | 09:37 |
| 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:38 |
| bauzas | I honestly don't know how to fix that | 09:39 |
| bauzas | stephenfin: tkajinam: you're unfortunately the last contributors of reno, so I probably need your help here :) | 09:40 |
| 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 |
| 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:42 |
| bauzas | I can try on my local git repo | 09:43 |
| *** Unknown123 is now known as Mike-- | 09:45 | |
| 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:49 |
| bauzas | I remembered reno using git tags | 09:50 |
| opendevreview | Sylvain Bauza proposed openstack/nova stable/2026.2: Fix graceful shutdown release note section https://review.opendev.org/c/openstack/nova/+/1007840 | 09:51 |
| 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 | 09:59 |
| opendevreview | Kamil Sambor proposed openstack/nova master: Replace StaticallyDelayingWrapper with futurist DelayingExecutor https://review.opendev.org/c/openstack/nova/+/997410 | 10:32 |
| 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:25 |
| bauzas | stephenfin: but how to fix the issue ? | 11:34 |
| bauzas | stephenfin: as you see the CI job doesn't create a right release note | 11:34 |
| 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 😕 | 11:58 |
| bauzas | I'm pretty sure this is due to the original patch | 11:59 |
| bauzas | it was tagged as a rc1 | 11:59 |
| bauzas | I mean, a 2026.2 RC1 tag, so it will use the original section | 12:00 |
| bauzas | so I guess we need to merge the backport before GA | 12:00 |
| bauzas | stephenfin: gibi: Uggla: actually this works, yoohoo https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_d1d/openstack/d1dbcca71faf4c35a7d480cf66c2df82/docs/2026.2.html | 12:01 |
| bauzas | I mean https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_d1d/openstack/d1dbcca71faf4c35a7d480cf66c2df82/docs/2026.2.html#known-issues | 12:02 |
| bauzas | can you please +2/+W both of the patches ? | 12:03 |
| bauzas | before GA | 12:03 |
| bauzas | elodilles: are you OK with that ? | 12:03 |
| stephenfin | I assume that CI result is from the backporT? | 12:04 |
| stephenfin | btw, this isn't the only issue in our release notes. Run `.tox/releasenotes/bin/reno lint` locally... | 12:05 |
| bauzas | stephenfin: sorry, indeed from https://zuul.opendev.org/t/openstack/build/d1dbcca71faf4c35a7d480cf66c2df82 | 12:06 |
| bauzas | stephenfin: yeah I saw most of issues this morning b/c I ran reno lint | 12:07 |
| elodilles | bauzas: with merging the reno fix to 2026.2 branch? | 12:07 |
| bauzas | elodilles: yeah | 12:07 |
| elodilles | yes, let's give it a try | 12:07 |
| stephenfin | bauzas: I'm not sure reno can fix that because it would break everyone with currently broken releasenotes. Maybe with a new major version though? | 12:08 |
| bauzas | elodilles: will we have a git tag for GA ? | 12:08 |
| bauzas | stephenfin: sorry, about which issues ? | 12:08 |
| elodilles | tomorrow, when we release, it will tag rc1 as final release, yes | 12:09 |
| stephenfin | okay, got to the bottom of it. The backport is needed because the sphinx extension is only reading the specific branch | 12:09 |
| bauzas | exactly | 12:09 |
| bauzas | elodilles: stephenfin: actually, given reno will use rc1 as GA, I guess we don't need to merge the backport before GA, we can first merge the master change and then the stable one when we want | 12:10 |
| elodilles | bauzas: though note, that it will tag rc1 as 34.0.0 | 12:10 |
| elodilles | so not the tip of stable/2026.2 | 12:10 |
| stephenfin | bauzas: there's zero risk to backporting this. I'd just merge it | 12:10 |
| bauzas | elodilles: I guess we'll see the relnote in 34.0.0 even if we merge the backport after | 12:10 |
| stephenfin | and yes, once the commit is on the branch it will appear. It doesn't need to be tagged | 12:11 |
| bauzas | as the original commit was merged before rc1 | 12:11 |
| stephenfin | arguably you don't even need the master commit. A stable-only one would likely do the job | 12:11 |
| bauzas | but we definitely need to fix both the master and the stable/2026.2 changes | 12:11 |
| bauzas | stephenfin: well, I'd prefer to fix both branches | 12:12 |
| bauzas | if people look at existing relnotes, they would find some wrong section name | 12:12 |
| stephenfin | I agree. I'm just noting it's not explicitly needed | 12:12 |
| bauzas | yeah yeah I was knowing | 12:12 |
| elodilles | bauzas: maybe we wait ~ an hour after the fix has landed on master branch, and we'll see | 12:12 |
| bauzas | elodilles: cool | 12:13 |
| bauzas | anyway, let's merge master first and we'll merge stable after | 12:13 |
| elodilles | but anyway, I'm ok with merging the reno fix to stable/2026.2 | 12:13 |
| bauzas | thanks stephenfin for +w'ing it btw. | 12:13 |
| stephenfin | nw | 12:14 |
| bauzas | elodilles: cool thanks, this will like any other backport | 12:14 |
| elodilles | i've +2d it now | 12:14 |
| bauzas | thanks | 12:15 |
| * gibi reading back | 12:25 | |
| gibi | OK I see both reno patch has the necessary votes | 12:26 |
| gibi | thanks folks for handling that | 12:26 |
| opendevreview | Merged openstack/nova master: Fix graceful shutdown release note section https://review.opendev.org/c/openstack/nova/+/1007837 | 13:05 |
| elodilles | i've +W'd -> https://review.opendev.org/c/openstack/nova/+/1007840 | 13:18 |
| gibi | elodilles: bauzas: thanks | 13:25 |
| opendevreview | Sylvain Bauza proposed openstack/nova master: Guard against deleting a concurrent request's BDM on timeout https://review.opendev.org/c/openstack/nova/+/1005727 | 13:27 |
| opendevreview | Sylvain Bauza proposed openstack/nova master: Prevent concurrent attach_volume with task_state guard https://review.opendev.org/c/openstack/nova/+/1006786 | 13:27 |
| opendevreview | Sylvain Bauza proposed openstack/nova master: Reject stale reserve_block_device_name RPC on compute https://review.opendev.org/c/openstack/nova/+/1006011 | 13:27 |
| elodilles | np | 13:35 |
| opendevreview | Kamil Sambor proposed openstack/nova master: Replace StaticallyDelayingWrapper with futurist DelayingExecutor https://review.opendev.org/c/openstack/nova/+/997410 | 13:44 |
| opendevreview | Merged openstack/nova stable/2026.2: Fix graceful shutdown release note section https://review.opendev.org/c/openstack/nova/+/1007840 | 13:48 |
| opendevreview | ribaudr proposed openstack/nova master: Add reproducer for bug #2163408: NUMA topology corrupted on failed live migration https://review.opendev.org/c/openstack/nova/+/1007871 | 13:58 |
| opendevreview | ribaudr proposed openstack/nova master: Fix NUMA topology corruption on failed live migration https://review.opendev.org/c/openstack/nova/+/1007872 | 13:58 |
| gmaan | bauzas: thanks for fixing the 'known_issue' releasenotes | 15:43 |
| bauzas | np | 15:43 |
| gmaan | I did not check the generated release ntoes that time otherwise could have caught | 15:43 |
| gmaan | bauzas: gibi so this is good to go now? https://review.opendev.org/c/openstack/nova/+/1007329 | 15:43 |
| opendevreview | Takashi Kajinami proposed openstack/nova master: Declare Python 3.14 support https://review.opendev.org/c/openstack/nova/+/1007898 | 15:44 |
| bauzas | I don't know why the CI job didn't said -1 for this but OK | 15:44 |
| gmaan | L11 (changed 'known_issues:') is not touched by this change so it is automatically merged ? let me rebase it explicitly anyways in case it create issue during merge | 15:45 |
| opendevreview | Ghanshyam Maan proposed openstack/nova stable/2026.2: Update graceful shutdown known issue to list resize case also https://review.opendev.org/c/openstack/nova/+/1007329 | 15:45 |
| gmaan | bauzas: ^^ should be good now | 15:45 |
| opendevreview | Takashi Kajinami proposed openstack/os-traits master: Update supported python versions according to tested runtimes https://review.opendev.org/c/openstack/os-traits/+/1007899 | 15:46 |
| bauzas | gmaan: I don't know if we can merge it before GA, elodilles are you OK with so ? | 15:46 |
| opendevreview | Takashi Kajinami proposed openstack/os-traits master: Update supported python versions https://review.opendev.org/c/openstack/os-traits/+/998011 | 15:47 |
| opendevreview | Takashi Kajinami proposed openstack/os-traits master: Update supported python versions https://review.opendev.org/c/openstack/os-traits/+/998011 | 15:47 |
| opendevreview | Takashi Kajinami proposed openstack/os-traits master: Update supported python versions https://review.opendev.org/c/openstack/os-traits/+/998011 | 15:48 |
| opendevreview | Takashi Kajinami proposed openstack/os-resource-classes master: Update supported python versions https://review.opendev.org/c/openstack/os-resource-classes/+/1007901 | 15:49 |
| opendevreview | Takashi Kajinami proposed openstack/os-resource-classes master: Migrate setup configuration to pyproject.toml https://review.opendev.org/c/openstack/os-resource-classes/+/1007903 | 15:51 |
| opendevreview | Takashi Kajinami proposed openstack/os-traits master: Migrate setup configuration to pyproject.toml https://review.opendev.org/c/openstack/os-traits/+/1007904 | 15:53 |
| opendevreview | Takashi Kajinami proposed openstack/os-resource-classes master: Migrate setup configuration to pyproject.toml https://review.opendev.org/c/openstack/os-resource-classes/+/1007903 | 15:54 |
| opendevreview | Takashi Kajinami proposed openstack/os-vif master: Declare Python 3.15 support https://review.opendev.org/c/openstack/os-vif/+/1007905 | 15:56 |
| opendevreview | Takashi Kajinami proposed openstack/os-traits master: Update supported python versions https://review.opendev.org/c/openstack/os-traits/+/998011 | 15:58 |
| opendevreview | Takashi Kajinami proposed openstack/os-traits master: Migrate setup configuration to pyproject.toml https://review.opendev.org/c/openstack/os-traits/+/1007904 | 15:58 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Func reproducer for bug/2168874 https://review.opendev.org/c/openstack/nova/+/1007917 | 16:13 |
| gibi | gmaan: +A | 16:14 |
| gibi | dansmith: bauzas: re cross cell cold migration / resize with PCI device. Cold migration fails with a separate bug https://bugs.launchpad.net/nova/+bug/2168874 but resize works. With resize I can reproduce the same PCI allocation leak if I inject a failure on the source. But the rollback + the dest compute periodic cleans the leak without an extra fix. | 16:16 |
| gibi | details with links to patches are here https://review.opendev.org/c/openstack/nova/+/1006003/comment/a47141f6_c90fb478/ | 16:16 |
| dansmith | I was just reading that | 16:16 |
| gmaan | gibi: thanks | 16:17 |
| gibi | take your time I need to drop. I will read back later | 16:17 |
| elodilles | bauzas: we merged the other reno fix patch anyway, so why not merge this one as well :) plus gibi already +2+W'd :D | 16:18 |
| elodilles | Uggla: about your comment on 2026.2 Hibiscus release patch: as Takashi wrote, we cannot change the SHA. that would need an RC2, but we are late for that and by merging the patch we already solved the "missing Known Issues section" problem during the day | 16:20 |
| dansmith | Uggla: are you going to update the ptg board to point to your non-standard etherpad link? The list https://ptg.opendev.org/etherpads.html still shows the default one so the real one is hard to find | 16:21 |
| bauzas | Uggla needs to join a irc chan and call the bot to change the URL | 16:22 |
| gmaan | elodilles: as you are here, once we update the releasenotes in stable, do we need release new version to reflect them in stable release notes? for example, i could not see the 'known_issue' keyword fix yet or need to wait for some sync job running in background? https://docs.openstack.org/releasenotes/nova/2026.2.html#known-issues | 16:22 |
| Uggla | elodilles, yes sorry I misunderstood something. That's ok | 16:22 |
| bauzas | dansmith: or I can do that but I don't know whether I still have superpowers for the ptgbot, hehe | 16:22 |
| dansmith | I'm also not sure why so much stuff is crossed out in the 2027.1 etherpad? | 16:23 |
| gmaan | dansmith: bauzas Uggla done, it should reflect now | 16:23 |
| elodilles | gmaan: i think it refreshes like hourly or so | 16:24 |
| gmaan | elodilles: cool | 16:24 |
| elodilles | Uggla: no problem o/ | 16:24 |
| bauzas | dansmith: probably coming from a copy/paste without removing some old content from 2026.2 PTG etherpad :) | 16:24 |
| dansmith | gmaan: looks wrong, points at meetpad not etherpad | 16:26 |
| gmaan | dansmith: it was overriden, now good | 16:27 |
| dansmith | gmaan: thanks | 16:27 |
| dansmith | Uggla: I added my cross-cell live migration topic to the end and also made a note (highlighting here for visibility) that it can't be scheduled on thursday | 16:28 |
| bauzas | dansmith: we fixed it in #openinfra-events | 16:28 |
| bauzas | ptgbot for the win | 16:29 |
| Uggla | dansmith ok thx. | 16:29 |
| opendevreview | Merged openstack/nova stable/2026.2: Update graceful shutdown known issue to list resize case also https://review.opendev.org/c/openstack/nova/+/1007329 | 17:36 |
| *** EugenMayer4401809 is now known as EugenMayer440180 | 17:48 | |
| *** EugenMayer4401800 is now known as EugenMayer440180 | 18:15 | |
| gmaan | gibi: you were right. we do not need stable release for release notes updates. Those are syned from branch - https://docs.openstack.org/releasenotes/nova/2026.2.html#known-issues | 18:31 |
| gmaan | Uggla: ^^ | 18:31 |
| *** hutnet5 is now known as hutnet | 21:49 | |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!