OpenStack creates a volume from an image failed with the VolumeDeviceNotFound error

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 67

Visibility:: Public

Votes:: 0

Category:: element-software

Specialty:: solidfire

Last Updated:

Applies to

Element Software
SolidFire

Issue

OpenStack creates a volume from an image and the SolidFire shows the API has been completed successfully:

9733 2024-03-05T05:42:34.315Z apiEvent API Call (CreateVolume)  1  { "success": true, "warning": { "unusedParameters": { "sliceCount": 1 } }, "params": { "enable512e": true, "qos": { "burstIOPS": 25000, "minIOPS": 100, "maxIOPS": 20000 }, "name": "clustername-6d70a4e6-a61c-43de-91e3-d9a781c205dd", "requestAPIVersion": "1.0", "totalSize": 8589934592, "sliceCount": 1, "attributes": { "cinder-name": "test_sysvol", "created_at": "2024-03-05T05:42:09+00:00", "is_clone": "False", "uuid": "6d70a4e6-a61c-43de-91e3-d9a781c205dd" }, "accountID": 1 }, "method": "CreateVolume", "context": { "ip": "10.xx.xx.xx", "authMethod": "Cluster", "user": "cinderuser" } }

The volume status on OpenStack shows as 'Error' and cinder-volume.log outputs the below error:

2024-03-05 05:49:33.485 40 ERROR cinder.volume.flows.manager.create_volume [req-edeb32ad-83c6-490b-8c7c-514dfc79356b 22193062483343998046f0c79b2f2fe9 882d1ddcc2a2492cb6702b4b53ff76d7 - - -] Failed to copy image 1e8d4a48-bbde-416f-b6fd-fff016673d6c to volume: 6d70a4e6-a61c-43de-91e3-d9a781c205dd: VolumeDeviceNotFound: Volume device not found at .

The ModifyVolume API(change capacity from 8GB to 30GB) is executed before the volume been created:

9735 2024-03-05T05:49:34.057Z apiEvent API Call (ModifyVolume)  1  { "success": true, "params": { "totalSize": 32212254720, "volumeID": 7, "requestAPIVersion": "5.0" }, "method": "ModifyVolume", "context": { "ip": "10.xx.xx.xx", "authMethod": "Cluster", "user": "cinderuser" } }