Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 510686[details]
vdsm-logs
Description of problem:
When exporting vm with 10 disks (cow sparse) to nfs export-domain with force override- export fails:
**the existent vm on the export domain is still displayed on getVmsInfo. but trying to import that vm fails (those volumes are partly deleted).
bccfa32c-5012-4a39-9f13-6a4ed75b4b45::ERROR::2011-06-30 16:32:05,322::task::865::TaskManager.Task::(_setError) Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 873, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 300, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/share/vdsm/storage/spm.py", line 115, in run
return self.func(*args, **kwargs)
File "/usr/share/vdsm/storage/spm.py", line 818, in moveImage
image.Image(repoPath).move(srcDomUUID, dstDomUUID, imgUUID, vmUUID, op, postZero, force)
File "/usr/share/vdsm/storage/image.py", line 563, in move
self.__templateRelink(dstSdUUID, imgUUID, leafVol.volUUID)
File "/usr/share/vdsm/storage/image.py", line 382, in __templateRelink
chList = vol.getAllChildrenList(self.repoPath, sdUUID, imgUUID, volUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 377, in getAllChildrenList
if SDF.produce(sdUUID).produceVolume(imgUUID, volid).getParent() == pvolUUID:
File "/usr/share/vdsm/storage/fileSD.py", line 135, in produceVolume
return fileVolume.FileVolume(repoPath, self.sdUUID, imgUUID, volUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 35, in __init__
volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
File "/usr/share/vdsm/storage/volume.py", line 111, in __init__
self.validate()
File "/usr/share/vdsm/storage/volume.py", line 117, in validate
self.validateImagePath()
File "/usr/share/vdsm/storage/fileVolume.py", line 480, in validateImagePath
raise se.ImagePathError(imageDir)
ImagePathError: Image path does not exist or cannot be accessed/created: ('/rhev/data-center/400b08e6-8d9d-4470-91b9-3b8076351314/7fea1def-0290-4279-9f52-341ff3c4a508/images/2bc5dfca-a04d-4b33-9d44-7e45f2a3a9e4',)
Version-Release number of selected component (if applicable):
vdsm-cli-4.9-79.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.export a based on template vm with 10 disks or more. (with or without exporting the template before)
2.export that same vm with force override option.
Actual results:
Export fails and corrupted vm is still displayed on getVmsInfo.
Expected results:
Additional info:
Another senario that cause the same behaviour is:
export a template and its child vm (with many disks)- one after another when they are already exist in the export domain.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHEA-2011-1782.html
Created attachment 510686 [details] vdsm-logs Description of problem: When exporting vm with 10 disks (cow sparse) to nfs export-domain with force override- export fails: **the existent vm on the export domain is still displayed on getVmsInfo. but trying to import that vm fails (those volumes are partly deleted). bccfa32c-5012-4a39-9f13-6a4ed75b4b45::ERROR::2011-06-30 16:32:05,322::task::865::TaskManager.Task::(_setError) Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 873, in _run return fn(*args, **kargs) File "/usr/share/vdsm/storage/task.py", line 300, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/share/vdsm/storage/spm.py", line 115, in run return self.func(*args, **kwargs) File "/usr/share/vdsm/storage/spm.py", line 818, in moveImage image.Image(repoPath).move(srcDomUUID, dstDomUUID, imgUUID, vmUUID, op, postZero, force) File "/usr/share/vdsm/storage/image.py", line 563, in move self.__templateRelink(dstSdUUID, imgUUID, leafVol.volUUID) File "/usr/share/vdsm/storage/image.py", line 382, in __templateRelink chList = vol.getAllChildrenList(self.repoPath, sdUUID, imgUUID, volUUID) File "/usr/share/vdsm/storage/fileVolume.py", line 377, in getAllChildrenList if SDF.produce(sdUUID).produceVolume(imgUUID, volid).getParent() == pvolUUID: File "/usr/share/vdsm/storage/fileSD.py", line 135, in produceVolume return fileVolume.FileVolume(repoPath, self.sdUUID, imgUUID, volUUID) File "/usr/share/vdsm/storage/fileVolume.py", line 35, in __init__ volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID) File "/usr/share/vdsm/storage/volume.py", line 111, in __init__ self.validate() File "/usr/share/vdsm/storage/volume.py", line 117, in validate self.validateImagePath() File "/usr/share/vdsm/storage/fileVolume.py", line 480, in validateImagePath raise se.ImagePathError(imageDir) ImagePathError: Image path does not exist or cannot be accessed/created: ('/rhev/data-center/400b08e6-8d9d-4470-91b9-3b8076351314/7fea1def-0290-4279-9f52-341ff3c4a508/images/2bc5dfca-a04d-4b33-9d44-7e45f2a3a9e4',) Version-Release number of selected component (if applicable): vdsm-cli-4.9-79.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.export a based on template vm with 10 disks or more. (with or without exporting the template before) 2.export that same vm with force override option. Actual results: Export fails and corrupted vm is still displayed on getVmsInfo. Expected results: Additional info: