Comment 11 for bug 1183283
Revision history for this message
| Kashyap Chamarthy (kashyapc) wrote Re: On a fresh devstack install, creating a new cinder volume fails with "Logical volume" exists. | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Ok, we seemed to have got this to a conclusion: Cinder is failing to copy the image to the volume.
Some contextual discussion from #openstack-qa:
========
...
jgriffith> kashyap: interesting
<jgriffith> kashyap: I didn't see your command entry asking it do do a copy of the image
<kashyap> Yeah
<jgriffith> kashyap: however that's what it appears to be doing ?
<jgriffith> kashyap: cinder allows you to write an image to a volume, but it's only when you specify an image-id on the create command
<jgriffith> kashyap: the failure is not the volume creation, it's the copy of the image to the volume
<kashyap> cinder create --display-name image_vol-test --image_id 52ff39a7-
<kashyap> jgriffith, Yes, I see it.
<jgriffith> kashyap: so the real bug is our failure to handle that propertly
<jgriffith> properly
<jgriffith> kashyap: if you want to modify the bug you entered I'll try and get it fixed in the next day or so
jgriffith> kashyap: yes, the summary and perhaps the title could be updated to point out exactly what the issue is, and you can assign it to me :)
========
========
$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
fedora 1 2 0 wz--n- 19.51g 0
stack-volumes 1 1 0 wz--n- 5.01g 4.01g
========