Bug 730763

Summary: spicec exits on failed migration because it doesn't keep connection to origin host
Product: Red Hat Enterprise Linux 6 Reporter: David Jaša <djasa>
Component: spice-clientAssignee: Uri Lublin <uril>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: cfergeau, dblechte, mkenneth, mkrcmari
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-21 15:43:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
spicec.log none

Description David Jaša 2011-08-15 17:15:31 UTC 
Description of problem:
... or it doesn't try to reconnect. spicec.log shows it pretty clearly (attached)

Version-Release number of selected component (if applicable):
spice-client-0.8.2-3.el6.x86_64

How reproducible:
always when migration fails and guest keeps running on originating host

Steps to Reproduce:
1. connect to VM
2. migrate VM to host where migration will fail but guest will keep running on original hypervisor
3.
  
Actual results:
spice client exits

Expected results:
spice client keeps connection

Additional info:
might be caused by some other component
probably is related to bug 730645
Comment 1 David Jaša 2011-08-15 17:16:00 UTC 
Created attachment 518295 [details]
spicec.log
Comment 2 RHEL Program Management 2011-10-07 16:06:55 UTC 
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.