Earlier  
Posted Nick Remark
#openstack-nova - 2024-09-16
11:57:17 gibi yeah that is the next step after the release then
11:57:33 sean-k-mooney i just told stephen about the job failure and he is fixign the typo
11:57:57 sean-k-mooney ah already done
11:59:04 sean-k-mooney i could make depends on work but i think its will take about the same amount of time to get resulst that way as waitign for the release
12:03:51 gibi yepp
12:05:01 sean-k-mooney the reset of the stuff in this chain is more of an experiment but i would appricate if we could merge https://review.opendev.org/c/openstack/nova/+/929353
12:06:24 sean-k-mooney it took a while to figure out why activatign the docs ven and running sphinx-build worked but tox -e docs didnt but it was trivial in the end
12:24:57 amorin hey nova team, is there any way to retrieve the nova instance az hints that were given during boot time other than looking in request_specs in DB? I can't find a way to retrieve that from the openstack/nova client/api
12:36:03 bauzas amorin: you need to upgrade to Caracal :)
12:36:07 bauzas amorin: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-2024-1-caracal-and-2024-2-dalmatian
12:36:32 bauzas by microversion 2.95, it will tell you whether the instance was pinned or not to an AZ
12:36:45 bauzas s/2.95/2.96 sorry
13:03:34 amorin bauzas, perfect! Will take a look
13:04:11 amorin do you have, by chance, link to the commits related to that? Maybe I can hack my antelope :)
13:09:58 amorin no worrie, found it :)
15:26:59 bauzas elodilles: frickler: so, about the OSC upgrade, I heard some good concerns
15:28:43 bauzas we haven't really tested the new OSC version and we're afraid to see *other* regressions
15:29:49 bauzas wouldn't it be *less* risky to let nova 2024.2 pin at OSC 6.x like we had before ?
15:30:13 bauzas (discussing it here and not in #openstack-release as I'd prefer nova folks to also discuss it)
15:34:33 elodilles are you aware of any (potential) regression? :-o
15:47:04 frickler bauzas: well the thing is that you cannot pin osc just for nova. if you pin it for everyone, you miss out a lot of the new that has been added. so less risky, yes, but less progress, too. but essentially that's a discussion to take up with the sdk team mostly I'd think
15:47:40 bauzas well, I already got scars about late bumps
15:48:15 bauzas and I have very little confidence of those kind of issues not to reproduce later
15:48:41 bauzas clearly the uc jobs are not proven robust enought
15:48:43 bauzas enough
15:48:50 melwitt was there not a requirements freeze weeks ago? https://releases.openstack.org/dalmatian/schedule.html#d-rf
15:51:32 frickler reqs freeze is for external deps, it explicitly does not include openstack deliverables
15:53:55 melwitt ok, I didn't see that mentioned in the link
15:56:44 melwitt it seems really late to be opening upper-constraints to not yet tested versions, regardless. IMHO
16:00:55 dansmith I missed that we're also discussing this here
16:01:23 dansmith frickler: it seems like anything that isn't being tested against master (i.e. nova's jobs uses cinder from master) then that's fine
16:01:29 bauzas most folks are now aware of the -release chat, let's move there
16:01:51 dansmith for things where development happens all cycle and then pops a release at the very end that everyone depends on, there needs to be an earlier deadline
16:14:28 JayF FWIW, Ironic is a cycle-with-intermediary, and we were commenting in our meeting on how we're going to frontrun our deadline as to avoid stress for folks. We do not have to deliver a final release until sometime next week. Thinking about it, I'm not sure that significant misalignment in deadlines makes sense.
16:47:24 dansmith JayF: but we also test nova master against ironic master right?
16:47:35 JayF Yes, that's what I said, we cross-test
16:48:16 JayF but this is still a gap in how we do planning, if other project are -with-intermeidary (tbh I don't know if they are)
16:48:56 dansmith yeah, that's a much better place to be in than what we're discussing here, which is project that is coordinated-released but where nobody tests against its master until the last minute (apparently)
#openstack-nova - 2024-09-17
06:44:41 opendevreview ribaudr proposed openstack/nova master: Amend ShareMappingStatus due to asynchronous call https://review.opendev.org/c/openstack/nova/+/908864
06:44:41 opendevreview ribaudr proposed openstack/nova master: Amend DB model add a unique constraint. https://review.opendev.org/c/openstack/nova/+/912518
06:44:42 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (manila abstraction) https://review.opendev.org/c/openstack/nova/+/831194
06:44:42 opendevreview ribaudr proposed openstack/nova master: Use client token when talking to manila https://review.opendev.org/c/openstack/nova/+/925277
06:44:43 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (drivers and compute manager part) https://review.opendev.org/c/openstack/nova/+/833090
06:44:43 opendevreview ribaudr proposed openstack/nova master: Mounting the shares as part of the initialization process https://review.opendev.org/c/openstack/nova/+/880075
06:44:44 opendevreview ribaudr proposed openstack/nova master: Deletion of associated share mappings on instance deletion https://review.opendev.org/c/openstack/nova/+/881472
06:44:44 opendevreview ribaudr proposed openstack/nova master: Add metadata for shares https://review.opendev.org/c/openstack/nova/+/850500
06:44:45 opendevreview ribaudr proposed openstack/nova master: Add share_info parameter to reboot method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/854823
06:44:45 opendevreview ribaudr proposed openstack/nova master: Support rebooting an instance with shares (compute manager part) https://review.opendev.org/c/openstack/nova/+/854824
06:44:47 opendevreview ribaudr proposed openstack/nova master: Add share_info parameter to resume method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/860284
06:44:47 opendevreview ribaudr proposed openstack/nova master: Support resuming an instance with shares (compute manager part) https://review.opendev.org/c/openstack/nova/+/860285
06:44:49 opendevreview ribaudr proposed openstack/nova master: Add helper methods to rescue/unrescue shares https://review.opendev.org/c/openstack/nova/+/860286
06:44:49 opendevreview ribaudr proposed openstack/nova master: Support rescuing an instance with shares https://review.opendev.org/c/openstack/nova/+/860287
06:44:51 opendevreview ribaudr proposed openstack/nova master: Allow to mount manila share using Cephfs protocol https://review.opendev.org/c/openstack/nova/+/883862
06:44:51 opendevreview ribaudr proposed openstack/nova master: Check shares support (compute manager) https://review.opendev.org/c/openstack/nova/+/885751
06:44:53 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (API) https://review.opendev.org/c/openstack/nova/+/836830
06:44:53 opendevreview ribaudr proposed openstack/nova master: Add helper methods to attach/detach shares https://review.opendev.org/c/openstack/nova/+/885753
06:44:55 opendevreview ribaudr proposed openstack/nova master: Add instance.share_attach notification https://review.opendev.org/c/openstack/nova/+/850501
06:44:55 opendevreview ribaudr proposed openstack/nova master: Add instance.share_detach notification https://review.opendev.org/c/openstack/nova/+/851028
06:44:57 opendevreview ribaudr proposed openstack/nova master: Add shares to InstancePayload https://review.opendev.org/c/openstack/nova/+/851029
06:44:57 opendevreview ribaudr proposed openstack/nova master: Add instance.share_attach_error notification https://review.opendev.org/c/openstack/nova/+/860282
06:44:59 opendevreview ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283
06:44:59 opendevreview ribaudr proposed openstack/nova master: Reports instance events to the DB regarding attaching and detaching a share https://review.opendev.org/c/openstack/nova/+/927088
06:45:01 opendevreview ribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working. https://review.opendev.org/c/openstack/nova/+/852086
06:45:01 opendevreview ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087
06:45:03 opendevreview ribaudr proposed openstack/nova master: Docs about Manila shares API usage https://review.opendev.org/c/openstack/nova/+/871642
10:29:50 zigo Hi there! When should I expect the RC1 for Nova?
10:29:59 zigo What's blocking?
10:41:17 opendevreview Merged openstack/placement stable/2024.2: Update .gitreview for stable/2024.2 https://review.opendev.org/c/openstack/placement/+/929290
10:41:18 opendevreview Merged openstack/placement stable/2024.2: Update TOX_CONSTRAINTS_FILE for stable/2024.2 https://review.opendev.org/c/openstack/placement/+/929291
10:51:24 stephenfin zigo: https://review.opendev.org/c/openstack/requirements/+/929504
11:06:17 tosky uhm, is there a bug which tracks the failure of nova-live-migration?
11:15:07 zigo stephenfin: FYI, I have all packages ready for Dalmatian but Nova, and I'm not affected by the issue with openstackclient (since 7.1.1 is there it's going to be used).
11:15:28 zigo Maybe I should package tip of master? Or is this already in a stable branch?
11:15:42 stephenfin it's already in a stable branch
11:15:48 zigo Ok, thanks.
11:16:12 zigo I'll do an ~rc1~git.<something> then.
11:17:57 zigo Not correct, I can't see a stable/2024.2 branch at https://opendev.org/openstack/nova
11:18:16 stephenfin I'm talking about OSC
11:18:24 zigo Oh... :P
11:18:30 zigo So nova is still on master, then I guess.
11:36:17 gibi just to set expectations after https://review.opendev.org/c/openstack/requirements/+/929504 lands we have at least 3 regression bug fixes lined up to land before we can cut RC1.
11:46:44 elodilles gibi or bauzas or other cores o:) when you have time, could you please do a quick review on these reno patches? https://review.opendev.org/c/openstack/python-novaclient/+/928366 and https://review.opendev.org/c/openstack/placement/+/929292
11:52:35 gibi on it
11:53:17 gibi I lost, stephenfin was faster :)
11:53:35 stephenfin 🥷
11:53:43 gibi :)
12:00:15 opendevreview Merged openstack/python-novaclient master: Update master for stable/2024.2 https://review.opendev.org/c/openstack/python-novaclient/+/928366
12:01:08 opendevreview Merged openstack/placement master: Update master for stable/2024.2 https://review.opendev.org/c/openstack/placement/+/929292
12:03:55 elodilles thx :]
14:40:37 zigo https://paste.opendev.org/show/bSMhXjOBcgfTTiNF0s1I/ <--- Is this a new behavior expected in Dalmatian ?
14:40:37 zigo If I provide --domain it works ...
14:53:36 sean-k-mooney i dont know but the keyston folks might. i doubt it woudl hav echanged but its possible
14:59:21 frickler zigo: sean-k-mooney: that's a bug in OSC, see https://review.opendev.org/c/openstack/python-openstackclient/+/929456
14:59:35 zigo Yeah, found the patch.
14:59:37 zigo Thanks.
14:59:44 zigo I'm already building OSC with it.
15:00:14 sean-k-mooney frickler: so we would need another osc release for that right
15:00:19 sean-k-mooney 7.1.2
15:00:26 zigo Agreed.
15:05:51 frickler I've been wondering whether the bug is critical enough to warrant another OSC release right away or whether it could wait until 2024.2 is out, but likely you're right

Earlier   Later