Resize attached volume with fiberchannel

Bug #1940521 reported by Aleksey Myltsev
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Triaged
Medium
Unassigned

Bug Description

We use volume_backed instances.
After live migration in connection_info desapiaring information about "device_path".
Resizing of attached volumes failed because in debug message try to get "device_path".

--- /usr/lib/python3/dist-packages/nova/virt/libvirt/volume/fibrechannel.py 2021-05-26 16:14:34.000000000 +0300
+++ /usr/lib/python3/dist-packages/nova/virt/libvirt/volume/fibrechannel_new.py 2021-05-26 16:14:38.000000000 +0300
@@ -80,6 +80,6 @@
         LOG.debug("calling os-brick to extend FC Volume", instance=instance)
         new_size = self.connector.extend_volume(connection_info['data'])
         LOG.debug("Extend FC Volume %s; new_size=%s",
- connection_info['data']['device_path'],
+ connection_info['volume_id'],
                   new_size, instance=instance)
         return new_size

I think change device_path to volume_id will be better and do not rise this exception.

Release Victoria.
Storage Huawei Dorado V3

Revision history for this message
Aleksey Myltsev (amyltsev) wrote :
description: updated
Revision history for this message
Balazs Gibizer (balazs-gibizer) wrote :

Looks like a valid bug. Feel free to propose the patch to review.opendev.org

Changed in nova:
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.