Earlier  
Posted Nick Remark
#openstack-nova - 2024-03-12
10:09:08 opendevreview ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283
10:09:10 opendevreview ribaudr proposed openstack/nova master: Docs about Manila shares API usage https://review.opendev.org/c/openstack/nova/+/871642
10:09:10 opendevreview ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087
10:09:12 opendevreview ribaudr proposed openstack/nova master: Amend DB model add a unique constraint. https://review.opendev.org/c/openstack/nova/+/912518
13:58:12 opendevreview ribaudr proposed openstack/nova master: Fix: Live migrating to a host with cpu_shared_set configured will now update the VM's configuration accordingly. https://review.opendev.org/c/openstack/nova/+/903706
13:58:12 opendevreview ribaudr proposed openstack/nova master: Fix [backport]: Live migrating to a host with cpu_shared_set configured will now update the VM's configuration accordingly. https://review.opendev.org/c/openstack/nova/+/877773
15:34:39 fwiesel Hi, regarding the bug report (https://bugs.launchpad.net/nova/+bug/2055700) (ServerActionsV293TestJSON.test_rebuild_volume_backed_server). I think, I do now why I get the exception. What I don't know is, how that is ever suppose to work with other hypervisors.
15:36:21 fwiesel ComputeManager._rebuild_default_impl is calling driver.destroy on the instance, and *then* calls a volume detach. That raises an InstanceNotFound in the vmwareapi driver, and I don't know how it should not.
15:37:04 fwiesel Here is the destroy: https://opendev.org/openstack/nova/src/branch/master/nova/compute/manager.py#L3695-L3701
15:37:35 fwiesel Then the call to _rebuild_volume_backed_instance (https://opendev.org/openstack/nova/src/branch/master/nova/compute/manager.py#L3714-L3715)
15:38:12 fwiesel Which in turn calls _detach_root_volume (https://opendev.org/openstack/nova/src/branch/master/nova/compute/manager.py#L3591)
15:38:55 fwiesel And that unsurprisingly calls driver.detach_volume (https://opendev.org/openstack/nova/src/branch/master/nova/compute/manager.py#L3556-L3557)
15:49:08 fwiesel I am unclear on how that is supposed to work. If you destroy an instance, my expectation would be that the driver does report InstanceNotFound when you do further operations on it. Apparently that is not the case with libvirt. What path will get triggered there?
15:51:26 bauzas reminder: nova meeting in 10 mins
15:51:58 bauzas fwiesel: I'm currently working hard but we could discuss this in the meeting
15:56:10 fwiesel Sure, no hurry from my side. I am also fine doing it via the bug-report.
16:01:09 opendevmeet The meeting name has been set to 'nova'
16:01:09 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:09 opendevmeet Meeting started Tue Mar 12 16:01:09 2024 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:09 bauzas #startmeeting nova
16:01:12 elodilles o/
16:01:13 bauzas hey folks
16:01:16 dansmith o/
16:01:17 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:28 fwiesel o/
16:02:13 auniyal o/
16:02:22 gibi o/
16:02:39 bauzas okay, let's start
16:03:00 bauzas #topic Bugs (stuck/critical)
16:03:06 bauzas #info Two Critical bugs
16:03:11 bauzas #link https://bugs.launchpad.net/nova/+bug/2052915
16:03:15 bauzas #link https://bugs.launchpad.net/nova/+bug/2056613
16:03:45 bauzas for the first one, AFAIK, we no longer have a problem
16:03:52 bauzas so we could close it
16:04:13 bauzas elodilles: ^
16:04:54 elodilles well nova-grenade-multinode is not failing
16:05:21 elodilles but that's not neutron-ovs-grenade-*
16:06:05 bauzas are we running those jobs in Nova ? I don't find so
16:06:15 elodilles so if nova was linked due to nova-grenade-multinode then we can close
16:06:24 elodilles otherwise we don't even run those jobs
16:06:32 bauzas OK, I'll close this for nova
16:06:37 elodilles +1
16:07:54 bauzas okay, next one https://bugs.launchpad.net/nova/+bug/2056613
16:08:41 bauzas that one is not really a Critical bug
16:09:13 bauzas if it's because we want to make sure we can merge the changes before rc1, we'll discuss this later in the meeting
16:09:43 bauzas so I'll move that bug to High and we'll add that bug report to the new rc etherpad I just created
16:09:59 gibi If we merge it for rc1 regardless of the priorityh then Im OK to drop the priority
16:10:59 bauzas in general, Critical priority for bugs are for either gate failures or if the issue is related to some API that everyone uses, say an user
16:11:13 bauzas for example, some bug with the create API
16:11:38 bauzas so moving it down to High and adding it to the etherpad
16:13:00 bauzas #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 65 new untriaged bugs (-10 since the last meeting)
16:13:13 bauzas I did a bit of triage for some
16:14:02 bauzas gibi: would you be okay to triage some bugs for next week ?
16:14:26 gibi I don't feel the power sorryj
16:14:44 Uggla o/
16:14:54 gibi but you can ping me with specific questions
16:15:38 bauzas okay, then I'll continue to use the baton for next week
16:15:50 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:15:57 bauzas #info bug baton is bauzas
16:16:13 bauzas #topic Gate status
16:16:17 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:16:22 bauzas #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:16:29 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:16:36 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:16:45 bauzas all periodics are green
16:16:57 bauzas anything people want to discuss about gate failures ?
16:16:59 sean-k-mooney cool including the ironic one
16:17:36 sean-k-mooney yep https://zuul.openstack.org/build/429f833ce05748d0a840d0c8ac18b726
16:17:49 bauzas yup I was about to reply
16:18:32 bauzas anything else to talk about CI ?
16:19:19 bauzas looks not, moving on then
16:19:26 bauzas #topic Release Planning
16:19:30 bauzas some important notes
16:19:36 bauzas #link https://releases.openstack.org/caracal/schedule.html#nova
16:19:41 bauzas #info RC1 planned this week
16:20:03 bauzas and then, the magic etherpad I just created :
16:20:09 bauzas #link https://etherpad.opendev.org/p/nova-caracal-rc-potential
16:20:31 bauzas as you can see, there is a long list of TODOs against patches we need to merge before RC1
16:20:53 bauzas that's my duty, I'll ensure either we already have them or I'll create them
16:21:03 dansmith um,
16:21:11 bauzas and then I'll ping some folks to make sure we can merge them before RC1
16:21:14 dansmith not just patches to review, but patches to *write* yeah?
16:21:30 dansmith unless I'm looking at the wrong "long list" :)
16:21:35 bauzas dansmith: yup, but if they don't exist, I'll create them tonight
16:21:43 dansmith okay
16:21:56 bauzas TODOs are mostly "I don't know if takashi created them yet"
16:22:08 bauzas if we want to be honest :D
16:22:38 bauzas those are quite simple to do, we have some pattern for every of them
16:22:58 bauzas so, yeah, cores, please understand that if I ping you for RC1 changes, those are a bit important
16:23:14 bauzas about one
16:23:23 bauzas #link https://review.opendev.org/c/openstack/releases/+/912480 Cycle highlights
16:23:37 gibi feel free to ping
16:23:38 bauzas cores and others, feel free to review that patch today if you can
16:24:05 bauzas that's the cycle highlights, I'll copy them to the prelude as soon as we merge the highlights
16:24:35 elodilles bauzas: i can approve it, unless you want to fix the nits
16:24:43 bauzas elodilles: I'll do the nits
16:24:47 elodilles +1
16:24:54 elodilles then i'll wait :]
16:24:58 bauzas it's quite a marketing document
16:25:23 elodilles indeed

Earlier   Later