Red Hat Bugzilla – Bug 878064
engine: Error while executing action SetVmTicket: Unexpected exception
Last modified: 2013-06-10 16:34:58 EDT
Created attachment 647824 [details] logs Description of problem: TimeoutError: Timed out during operation: cannot acquire state change lock in vdsm for setVmTicket has an exception error in UI. Version-Release number of selected component (if applicable): si24.2 How reproducible: 100% Steps to Reproduce: 1. create and run a vm 2. live migrate the vm -> once snapshot is created try to migrate the vm to a different host 3. after migration fails try to open spice monitor to vm Actual results: Unexpected exception in engine log will prompt error in UI: Error while executing action SetVmTicket: Unexpected exception Expected results: we need to have a clear error for the exception Additional info: logs
dafna, can you please clarify the scenario? what is "once snapshot is created"
when we move a disk we create a live snapshot. once snapshot is created -> after the live snapshot is created for the live migration.
the error will not occur in that scenario after bug 872277 resolution. still worth catching this Monitor timeout exception and set the correct message in VDSM error object
mistakenly closed it. proposed patch for VDSM and engine: http://gerrit.ovirt.org/#/q/topic:878064,n,z
This bug is currently attached to errata RHBA-2012:14332. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
there is CanDoAction added to the live storage migration + live migration. I tested after the CanDoAction and after the live storage migration ended + live migration of the vm. we cannot connect to the graphic server after the vm migrated but no exception moving to verified.
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/RHSA-2013-0886.html