So there are actually probably about 3 bugs here.
The first is a WUI issue. I'm seeing that same error although it doesn't seem to affect the actual migration call.
There is a connection issue which is likely a kerberos problem.
Then there is the virDomainMigrate call failing which is a more serious problem with libvirt itself. Apparently there are issues with the current libvirt which are being addressed.
I have not been able to reproduce the connection failed problem. I'm going to leave everything running for a while and see if maybe the tickets are expiring or something.

We may need to pull in Chris' "tunneled migration" patch to get qmf migration to really work properly, although it is going to change before it goes upstream in libvirt (but at least we could test the concept).

OK, I've just made a series of changes:
- Storage pool mounting was done with random strings, this is now changed to uniquely identify the mount but the mount point will be the the same across all nodes.
- I updated to the latest libvirtd (it's in the ovirt repo).
- I modified libvirt-qpid so that it can now do the migration from node to node!
So these changes should fix all the above issues.

This bugzilla product/component combination is no longer used: ovirt bugs are tracked under the bugzilla product 'oVirt'. If this bug is still valid, please reopen and set the correct product/component.

Note

You need to
log in
before you can comment on or make changes to this bug.