Bug 1196678 - Failing to migrate VMs between FC19 and FC20 hosts
Summary: Failing to migrate VMs between FC19 and FC20 hosts
Keywords:
Status: CLOSED DUPLICATE of bug 1018178
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Dan Kenigsberg
QA Contact: Gil Klein
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-26 14:18 UTC by Brian Sipos
Modified: 2015-03-23 12:56 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-23 12:56:11 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
engine log from a few seconds before the failed migration (10.75 KB, text/plain)
2015-03-02 14:09 UTC, Brian Sipos
no flags Details
migration-source VDSM log from up to two minutes before the failed migration (1.21 KB, text/plain)
2015-03-02 14:10 UTC, Brian Sipos
no flags Details

Description Brian Sipos 2015-02-26 14:18:06 UTC
Description of problem:
I currently have ovirt-engine running on a CentOS VM and two ovirt hosts (one on Fedora 19 on on Fedora 20).

Version-Release number of selected component (if applicable):
ovirt-engine (on EL6) is 3.5.1.1

How reproducible:
Consistently, for migration in either direction.

Steps to Reproduce:
1. Start up a VM, it is allocated to a particular host.
2. Select the running VM in the VM list and select Migrate.
3. Observe the ovirt-engine log contains (with timestamps less than a minute apart):
Migration started (VM: vm, Source: host-fc20, Destination: host-fc19, User: ...).
Migration failed due to Error: Fatal error during migration. Trying to migrate to another Host (VM: vm, Source: host-fc20, Destination: host-fc19).

Actual results:
The VM fails to migrate.

Expected results:
The VM should end up running on the alternate host.

Additional info:
I can provide individual "vdsm.log" from the hosts or "engine.log" from the engine as needed.
If this matters, the cluster is running in compatibility version 3.4 since it was created when 3.4 was latest version. I should be able to bump this compat. version although I have never attempted to do so.

Comment 1 Omer Frenkel 2015-03-01 08:06:00 UTC
please attach engine.log and vdsm.log from source host for the time of the migration.
thanks!

Comment 2 Brian Sipos 2015-03-02 14:09:11 UTC
Created attachment 997101 [details]
engine log from a few seconds before the failed migration

Comment 3 Brian Sipos 2015-03-02 14:10:04 UTC
Created attachment 997102 [details]
migration-source VDSM log from up to two minutes before the failed migration

Comment 4 Brian Sipos 2015-03-02 19:08:09 UTC
Upon further inspection, it appears that I have blocked the libvirt port (TCP 16514) on one host's firewalls. Now that the port is open, I am running across what appears to be a known FC19 issue in libvirtd (https://bugzilla.redhat.com/show_bug.cgi?id=1018178).

Comment 5 Michal Skrivanek 2015-03-23 12:56:11 UTC
ok. thanks for finding out. no need to track it again here...

*** This bug has been marked as a duplicate of bug 1018178 ***


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