Monday, 2025-03-03

opendevreviewCallum Dickinson proposed openstack/nova master: Fix image ID in libvirt metadata when unshelving  https://review.opendev.org/c/openstack/nova/+/94297300:09
opendevreviewCallum Dickinson proposed openstack/nova master: Add image meta to libvirt XML metadata  https://review.opendev.org/c/openstack/nova/+/94276603:00
opendevreviewCallum Dickinson proposed openstack/nova master: Add more flavor metadata to libvirt guest XML  https://review.opendev.org/c/openstack/nova/+/94297405:03
opendevreviewTakashi Kajinami proposed openstack/nova master: Drop quota options from the DEFAULT section  https://review.opendev.org/c/openstack/nova/+/94313108:36
opendevreviewTobias Urdin proposed openstack/nova master: wip: Reserve volumes when doing instance resize  https://review.opendev.org/c/openstack/nova/+/94298509:04
tobias-urdinwhen testing above^ patch i just realized that you cannot reserve a cinder volume when status is in-use, based on the issue described there i guess the only two alternatives to solve the problem in that patch is either 1) add a simple check for volume status and live with the potential race condition between check of volume status and actual _terminate_volume_connections call09:08
tobias-urdinor 2) catch InvalidVolume exceptions directly in _terminate_volume_connections and try to rollback volume attachments and then raise a InstanceFaultRollback exception, anybody else has any better ideas?09:08
opendevreviewribaudr proposed openstack/nova master: Update driver to map the targeted address for SR-IOV PCI devices  https://review.opendev.org/c/openstack/nova/+/94214709:37
opendevreviewribaudr proposed openstack/nova master: FUP improve comment accuracy and variable naming for tag removal  https://review.opendev.org/c/openstack/nova/+/94312409:37
sean-k-mooneytobias-urdin: i have not looked into your patches yet but waht was the problem you were tryign to resolve?09:44
sean-k-mooneytobias-urdin: i vagely saw them coming in last week but didnt have time to read them09:44
sean-k-mooneytobias-urdin: oh ok... so thisi is kind of a cinder bug09:46
sean-k-mooneytobias-urdin: so the problem is that cinder does not knwo that nova is in the middle of doing a resize and nova does not know that cidner wants to do a backup09:46
tobias-urdinsean-k-mooney: if i try to resize and instance it goes to ERROR and needs operator to restore it (shutdown has already been called) because attachment_create() volume API raises InvalidVolume when an attached volume has backing-up status09:46
sean-k-mooneyso we can get in a broken state09:46
sean-k-mooneytobias-urdin: well you can resize instnace with cinder volumes09:47
sean-k-mooneythat not the problem its because you also happen to have a cinder backup at the same time09:47
sean-k-mooneytobias-urdin: both nova and cidner backup exepct to be the only thing modifying the volume state when doign a resize or backup09:48
tobias-urdinyea, i could just loop volumes and check status in the context and raise InstanceFaultRollback i guess for resize to not hit it, but there would still be a race between me checking the status and attachment code being called in resize09:49
sean-k-mooneythat not really the fix09:49
tobias-urdini was hoping i could reserve the volumes before starting the operation, but my research failed because it didn't accommodate for in-use not being possible on in-use volume :(09:49
sean-k-mooneywe either need nova to annotate the volume with somethjing to indicate that we are migrating09:50
sean-k-mooneyor we need to have cidner check the status of attached instnace before doing a backup09:50
sean-k-mooneytobias-urdin: is cidner backup changing the state of the volume to something other then inuse09:51
tobias-urdinyes "backing-up" is set09:51
sean-k-mooneyright os that also a bug09:51
sean-k-mooneyonce a volume is attached to a nova instnace we do not exect the voluem status to change unless its via a call to the nova api09:52
sean-k-mooneyso form a nova perspecitve it should remain in use09:52
sean-k-mooneyit would be fine to have a seperate task_state that backing-up09:53
sean-k-mooneybut if cidner want to modify it they need to make the attchment api treat backing-up the same as in-use09:54
tobias-urdinthat actually makes more sense09:54
sean-k-mooneywe have a bunch of task_state that we translate to "active" because semanticly external service should treat them the same09:55
sean-k-mooneyi dont know how to express that in cidner api but i think if they have internal states liek backing-up they may need a similar mechanisum09:56
sean-k-mooneylike this https://github.com/openstack/nova/blob/master/nova/api/openstack/common.py#L46-L6309:59
tobias-urdinsean-k-mooney: thanks for the directions! i will investigate further and see if i can find a better path forward10:03
sean-k-mooneyill try an comment on the bug and maybe a good dicusion for the ptg in a nova/cinder cross project if we dont have a path forward by then10:04
tobias-urdinsean-k-mooney: ack, looks like they account for some migration logic in _attachment_reserve() https://github.com/openstack/cinder/blob/master/cinder/volume/api.py#L240910:08
tobias-urdinso imo handling backing-up (if "previous status", that it sets back when backup is complete, is in-use) as if it were in-use makes sense10:09
sean-k-mooneytobias-urdin: https://bugs.launchpad.net/nova/+bug/2077512/comments/5 i tried to summeriese my toughts and i added cinder to the bug10:44
tobias-urdinsean-k-mooney: this is the real path forward https://review.opendev.org/c/openstack/cinder-specs/+/915973 instead of my new hack approach https://review.opendev.org/c/openstack/cinder/+/94317613:10
opendevreviewMerged openstack/nova master: Update driver to deal with managed flag  https://review.opendev.org/c/openstack/nova/+/93840513:54
sean-k-mooneytobias-urdin: ah yes that does seam to be adressign this edgecase14:04

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!