os_brick.exception.VolumeDeviceNotFound

Bug #2047312 reported by Dave West
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

Running OpenStack 2023.2 with Cinder and PureStorage Flash Array as the backend. I am leveraging NVMe/TCP as the protocol. I am able to create a blank volume on the FA through Horizon. If I mark that volume as bootable and create an instance with it, or create a volume with an image, the volumes fail.

The most prevalent error I get is: "raise exception.VolumeDeviceNotFound(device=target.nqn)#0122023-12-24 18:22:36.440 53820 ERROR oslo_messaging.rpc.server os_brick.exception.VolumeDeviceNotFound: Volume device not found at nqn.2010-06.com.purestorage:flasharray"

When the workflow kicks off, I can see the volume mounted on the host.

nvme list
Node Generic SN Model Namespace Usage Format FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1 /dev/ng0n1 0EC012D099B841EB Pure Storage FlashArray 0x3f 1.07 GB / 1.07 GB 512 B + 0 B 6.5.1

ls /dev/disk/by-id/nvm*
/dev/disk/by-id/nvme-Pure_Storage_FlashArray_0EC012D099B841EB /dev/disk/by-id/nvme-Pure_Storage_FlashArray_0EC012D099B841EB_63 /dev/disk/by-id/nvme-eui.003244296e0f444d24a9379600011caa

I tried turning on debugging and verbose loggin to see the commands being sent to help understand where the process is failing, but unable to see that.

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.