Created attachment 902185[details]
vdsm log
Description of problem:
When trying to activate volume using prepareVolume it fails with: ImagePathError: Image path does not exist or cannot be accessed/created: ('/rhev/data-center/32dab0ff-9eaa-41c7-ae50-4e6ef6355512/831ef374-8947-47f2-938f-5ec938f4fcef/images/8f3f3871-6aab-4f26-811f-c8e1803414fd',)
Version-Release number of selected component (if applicable):
vdsm-4.14.6-0.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
<python_snippet>
from vdsm import vdscli
spUUID='32dab0ff-9eaa-41c7-ae50-4e6ef6355512'
sdUUID='831ef374-8947-47f2-938f-5ec938f4fcef'
lockspace_volume_UUID='81fbcbaf-2264-4fa8-831f-da5bf9b5281b'
lockspace_image_UUID='8f3f3871-6aab-4f26-811f-c8e1803414fd'
con = vdscli.connect()
response = con.prepareVolume(
sdUUID,
spUUID,
lockspace_image_UUID,
lockspace_volume_UUID
)
print response
</python_snippet>
Actual results:
Volume not activated
Expected results:
Volume activated
Additional info:
The image did exist before vdsm restart. VDSM deactivated the volume because it doesn't know the volume and removed the image and is failing to activate it.
Steps to reproduce:
1. create a volume using createVolume() call from vdsm api
2. restart vdsm (which deactivates that volume)
3. try to call prepareVolume() to activate the volume created in step 1.
Comment 2Federico Simoncelli
2014-06-04 17:22:58 UTC
We should just tackle this with bug 1092166.
prepareVolume is not in use since a while and trying to fix it is probably more risky than just expose prepareImage.
or we can merge http://gerrit.ovirt.org/27880 because even if the prepareVolume (or Image) works it still means that at some point vdsm deactivated the volume which might be racy
Comment 4Federico Simoncelli
2014-06-05 10:49:08 UTC
Closing this as wontfix since prepareVolume is deprecated. We'll continue on bug 1092166. I already updated bug 1036731 to reflect the new dependency.
Created attachment 902185 [details] vdsm log Description of problem: When trying to activate volume using prepareVolume it fails with: ImagePathError: Image path does not exist or cannot be accessed/created: ('/rhev/data-center/32dab0ff-9eaa-41c7-ae50-4e6ef6355512/831ef374-8947-47f2-938f-5ec938f4fcef/images/8f3f3871-6aab-4f26-811f-c8e1803414fd',) Version-Release number of selected component (if applicable): vdsm-4.14.6-0.el6.x86_64 How reproducible: 100% Steps to Reproduce: <python_snippet> from vdsm import vdscli spUUID='32dab0ff-9eaa-41c7-ae50-4e6ef6355512' sdUUID='831ef374-8947-47f2-938f-5ec938f4fcef' lockspace_volume_UUID='81fbcbaf-2264-4fa8-831f-da5bf9b5281b' lockspace_image_UUID='8f3f3871-6aab-4f26-811f-c8e1803414fd' con = vdscli.connect() response = con.prepareVolume( sdUUID, spUUID, lockspace_image_UUID, lockspace_volume_UUID ) print response </python_snippet> Actual results: Volume not activated Expected results: Volume activated Additional info: The image did exist before vdsm restart. VDSM deactivated the volume because it doesn't know the volume and removed the image and is failing to activate it.