Bug 1022565
Summary: | client_migrate_info fails when r-v connects through vv file over SSL encryption | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Marian Krcmarik <mkrcmari> | |
Component: | spice-gtk | Assignee: | Marc-Andre Lureau <marcandre.lureau> | |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.5 | CC: | cfergeau, dblechte, marcandre.lureau, michal.skrivanek, mkrcmari, rbalakri | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | spice-gtk-0.22-1.el6 | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Migration of a VM with a client connected via mime connection file and SSL.
Consequence:
The migration falls back to non-seamless, because the CA isn't correctly copied form memory.
Fix:
Copy the CA on destination session.
Result:
The seamless migration can be realized with success.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1036833 (view as bug list) | Environment: | ||
Last Closed: | 2014-10-14 06:46:34 UTC | Type: | Bug | |
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: | 1036833 |
Description
Marian Krcmarik
2013-10-23 14:31:55 UTC
Is the client receiving a new ca-file when migrating with xpi? Do you know if the servers share the same CA? Could you get the log of G_MESSAGES_DEBUG=GSpiceController? This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. (In reply to Marc-Andre Lureau from comment #2) > Is the client receiving a new ca-file when migrating with xpi? receiving from where? from portal? I do not think so. > > Do you know if the servers share the same CA? Yes, They do. > > Could you get the log of G_MESSAGES_DEBUG=GSpiceController? I do not know how can that help, probably I could, but nothing happens in the log when migrating a VM which was connected through xpi. Ok, I guess that was fixed a while ago with.. commit 647344fa7513ef3c428cfbc4fc841d8bf29a0310 Author: Marc-André Lureau <marcandre.lureau> Date: Mon Jul 22 15:07:55 2013 +0200 session: copy "ca" property in copy ctor This fixes the GSpice-WARNING **: no cert loaded, when doing a seamless migration (when using the "ca" property). (In reply to Marc-Andre Lureau from comment #5) > Ok, I guess that was fixed a while ago with.. > > commit 647344fa7513ef3c428cfbc4fc841d8bf29a0310 > Author: Marc-André Lureau <marcandre.lureau> > Date: Mon Jul 22 15:07:55 2013 +0200 > > session: copy "ca" property in copy ctor > > This fixes the GSpice-WARNING **: no cert loaded, when doing a seamless > migration (when using the "ca" property). Why didn't it get into any build? you probably fixed it like 3 months ago? (In reply to Marian Krcmarik from comment #6) > > This fixes the GSpice-WARNING **: no cert loaded, when doing a seamless > > migration (when using the "ca" property). > > Why didn't it get into any build? you probably fixed it like 3 months ago? No idea, I guess I thought that was just a minor warning. will the fix take care of https://bugzilla.redhat.com/show_bug.cgi?id=1026474#c6 ? We cannot differentiate between disconnect and "hand over with a delay" (In reply to Michal Skrivanek from comment #8) > will the fix take care of > https://bugzilla.redhat.com/show_bug.cgi?id=1026474#c6 ? > We cannot differentiate between disconnect and "hand over with a delay" That's what I understand from David comment. I do not understand what's happening in guest in bug 1026474, but I read "switch host" method will cause an additional delay that triggers desktop lock-in. 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-2014-1487.html |