<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">In that case, this sounds like a bug to me related to lvm volumes. You should check the nova-compute.log from both hosts and the nova-conductor.log. If it isn’t obvious what the problem is, you should open a bug and attach as much info as possible.<div><br></div><div><div>Vish</div><div><br><div><div>On Jan 16, 2014, at 8:04 AM, Dan Genin <<a href="mailto:daniel.genin@jhuapl.edu">daniel.genin@jhuapl.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Thank you for replying, Vish. I did
sync and verified that the file was written to the host disk by
mounting the LVM volume on the host.<br>
<br>
When I tried live migration I got a Horizon blurb "Error: Failed
to live migrate instance to host" but there were no errors in
syslog.<br>
<br>
I have been able to successfully migrate a Qcow2 backed instance.<br>
Dan<br>
<br>
On 01/16/2014 03:18 AM, Vishvananda Ishaya wrote:<br>
</div>
<blockquote cite="mid:DD2AADF2-41B8-457C-B82D-0568981509D1@gmail.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>This is probably more of a usage question, but I will go
ahead and answer it.</div>
<div><br>
</div>
If you are writing to the root drive you may need to run the sync
command a few times to make sure that the data has been flushed to
disk before you kick off the migration.
<div><br>
</div>
<div>The confirm resize step should be deleting the old data, but
there may be a bug in the lvm backend if this isn’t happening.
Live(block) migration will probably be a bit more intuitive.</div>
<div><br>
</div>
<div>Vish</div>
<div>
<div>
<div>On Jan 15, 2014, at 2:40 PM, Dan Genin <<a moz-do-not-send="true" href="mailto:daniel.genin@jhuapl.edu">daniel.genin@jhuapl.edu</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<div bgcolor="#FFFFFF" text="#000000"> I think this
qualifies as a development question but please let me know
if I am wrong.<br>
<br>
I have been trying to test instance migration in devstack
by setting up a multi-node devstack following directions
at <a moz-do-not-send="true" href="http://devstack.org/guides/multinode-lab.html">http://devstack.org/guides/multinode-lab.html</a>.
I tested that indeed there were multiple availability
zones and that it was possible to create instances in
each. The I tried migrating an instance from one compute
node to another using the Horizon interface (I could not
find a way to <i>confirm</i><i> </i>migration, which is
a necessary step, from the command line). I created a test
file on the instance's ephemeral disk, before migrating
it, to verify that the data was moved to the destination
compute node. After migration, I observed an instance with
the same id active on the destination node but the test
file was not present.<br>
<br>
Perhaps I misunderstand how migration is supposed to work
but I expected that the data on the ephemeral disk would
be migrated with the instance. I suppose it could take
some time for the ephemeral disk to be copied but then I
would not expect the instance to become active on the
destination node before the copy operation was complete.<br>
<br>
I also noticed that the ephemeral disk on the source
compute node was not removed after the instance was
migrated, although, the instance directory was. Nor was
the disk removed after the instance was destroyed. I was
using LVM backend for my tests. <br>
<br>
I can provide more information about my setup but I just
wanted to check whether I was doing (or expecting)
something obviously stupid.<br>
<br>
Thank you,<br>
Dan<br>
</div>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a moz-do-not-send="true" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></div></body></html>