Bug 972696
Summary: | engine: after we fail to LSM a disk for a vm in pause state engine fails to clean cloneImageStructure task with ArrayIndexOutOfBoundsException: -1 (can't migrate disks because of orphan images on target domain) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Idith Tal-Kohen <italkohe> | ||||||
Component: | ovirt-engine | Assignee: | Daniel Erez <derez> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Aharon Canan <acanan> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 3.2.0 | CC: | abaron, acanan, acathrow, amureini, bazulay, cpelland, derez, dron, hateya, iheim, jkt, lpeer, mgoldboi, pzhukov, Rhev-m-bugs, scohen, yeylon, zdover | ||||||
Target Milestone: | --- | Keywords: | Triaged, ZStream | ||||||
Target Release: | 3.3.0 | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | storage | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: |
Previously, an exception was left in the engine logs when the engine failed to clean cloneImageStructure tasks with ArrayIndexOutOfBoundsException.
Such exceptions are now cleaned from the engine logs.
(Note: the images associated with such exceptions are still left on the target domains. Cleanup of target domains in such situations is expected to be implemented in a future version of Red Hat Enterprise Virtualization Manager.)
|
Story Points: | --- | ||||||
Clone Of: | 966618 | Environment: | |||||||
Last Closed: | 2013-07-16 13:41:06 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | 966618 | ||||||||
Bug Blocks: | 902971 | ||||||||
Attachments: |
|
Description
Idith Tal-Kohen
2013-06-10 12:25:31 UTC
Created attachment 766168 [details]
vdms log
Created attachment 766169 [details]
engine log
reproduce using sf18.2
logs attached
from logs -
468f6937-14cd-47b7-892b-406c46f167c1::ERROR::2013-06-27 17:23:53,557::task::850::TaskManager.Task::(_setError) Task=`468f6937-14cd-47b7-892b-406c46f167c1`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 857, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 318, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/share/vdsm/storage/securable.py", line 68, in wrapper
return f(self, *args, **kwargs)
File "/usr/share/vdsm/storage/sp.py", line 1773, in cloneImageStructure
image.Image(repoPath).cloneStructure(sdUUID, imgUUID, dstSdUUID)
File "/usr/share/vdsm/storage/image.py", line 649, in cloneStructure
self._createTargetImage(sdCache.produce(dstSdUUID), sdUUID, imgUUID)
File "/usr/share/vdsm/storage/image.py", line 517, in _createTargetImage
srcVolUUID=volParams['parent'])
File "/usr/share/vdsm/storage/blockSD.py", line 609, in createVolume
volUUID, desc, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/volume.py", line 418, in create
raise se.VolumeAlreadyExists(volUUID)
VolumeAlreadyExists: Volume already exists: ('3a31b139-b457-4989-941e-0fd99d5021e7',)
468f6937-14cd-47b7-892b-406c46f167c1::DEBUG::2013-06-27 17:23:53,558::task::869::TaskManager.Task::(_run) Task=`468f6937-14cd-47b7-892b-406c46f167c1`::Task._run: 468f6937-14cd-47b7-892b-406c46f167c1 () {} failed - stopping task
The original issue was fixed, the remaining issue is that vdsm does not clean up the leftovers of the disk on the target domain. Need to reproduce and understand under what conditions this happens. *** Bug 970974 has been marked as a duplicate of this bug. *** 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/RHBA-2013-1048.html |