Hide Forgot
Created attachment 925632 [details] engine log Description of problem: VDSGenericException, VDSErrorException and VdcBLLException occurs when poring off a vm during a live storage migration Version-Release number of selected component (if applicable): ovirt-engine-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Power off a vm during LSM 2. 3. Actual results: The above exceptions are raised Expected results: Should work with no exceptions Additional info:
Not sure it's worth the hassle - Daniel, please review?
On a failure of VdsCommand, we usually display the stack trace in the log for error investigation needs. @Allon - do you think we should obscure it specifically on live snapshot failure?
(In reply to Daniel Erez from comment #2) > On a failure of VdsCommand, we usually display the stack trace in the log > for error investigation needs. > @Allon - do you think we should obscure it specifically on live snapshot > failure? No.
guys, This is a bug but I agree the severity is low and not high, also we can go with wontfix instead notabug. maybe we should keep it to futurerelease?
(In reply to Aharon Canan from comment #4) > guys, > > This is a bug but I agree the severity is low and not high, > also we can go with wontfix instead notabug. > > maybe we should keep it to futurerelease? Any VDS command can fail at any point in time if the VM is shut down unexpectedly - hotplug, hibernate, live snapshot, migrate - you name it. In case this happens, we'd want the stacktrace in the log in order to investigate.