Bug 737921
Summary: | Spice password on migration target expires before Spice client is connected | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Yonit Halperin <yhalperi> |
Component: | qemu-kvm | Assignee: | Yonit Halperin <yhalperi> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 6.1 | CC: | abaron, acathrow, bazulay, berrange, cfergeau, dallan, danken, dblechte, dyuan, iheim, jdenemar, juzhang, kraxel, marcandre.lureau, michen, minovotn, mjenner, mkenneth, mkrcmari, mzhan, qzhang, rwu, tburke, uril, vbian, virt-maint, weizhan, yhalperi |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-0.12.1.2-2.206.el6 | Doc Type: | Bug Fix |
Doc Text: |
Cause
Spice client connected to the migration target only after migration completed.
However, the ticket on the target was set before migration started.
Consequence
If (migration_time > ticket_expiration_time) - spice client failed to connect to the target and aborted.
Fix
spice server informs spice client to connect to the target before migration starts, upon the client_migrate_info command.
client_migrate_info was turned to an async command.
spice server waits till the client performed the initial connection (or a timeout), and then calls the completion callback of client_migrate_info.
Result
Spice client is connected to the migration target after migration.
|
Story Points: | --- |
Clone Of: | 725009 | Environment: | |
Last Closed: | 2011-12-06 16:03:09 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: | |||
Bug Depends On: | |||
Bug Blocks: | 725009, 727602, 731472, 738262, 738268 |
Comment 6
Qunfang Zhang
2011-10-19 08:11:11 UTC
Moving to ON_QA because Errata Tool did not do it Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause Spice client connected to the migration target only after migration completed. However, the ticket on the target was set before migration started. Consequence If (migration_time > ticket_expiration_time) - spice client failed to connect to the target and aborted. Fix spice server informs spice client to connect to the target before migration starts, upon the client_migrate_info command. client_migrate_info was turned to an async command. spice server waits till the client performed the initial connection (or a timeout), and then calls the completion callback of client_migrate_info. Result Spice client is connected to the migration target after migration. 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-2011-1531.html |