<div dir="ltr">Kekane,<div><br></div><div>Hi,</div><div><br></div><div>This setting, how does it display in the "nova show $UUID" or in the "openstack server show $UUID"? Ie, I don't want a VM showing ERROR state if the VM itself is not in error. A failed migration doesn't leave the VM down (well, not always) but error generally implies it is down. If this is more of an internal status, then +1. I'll look at the code shortly but wanted to get a reply off first. </div><div><br></div><div>ALSO: It would have been very very helpful to see "live-migration" in the subject line.</div><div><br></div><div>-d</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 11, 2016 at 12:55 AM, Kekane, Abhishek <span dir="ltr"><<a href="mailto:Abhishek.Kekane@nttdata.com" target="_blank">Abhishek.Kekane@nttdata.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Operators,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Could you please provide your opinion on below mail. I need to discuss this in coming nova meeting (12 May, 2016).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thank you,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Abhishek Kekane<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kekane, Abhishek [mailto:<a href="mailto:Abhishek.Kekane@nttdata.com" target="_blank">Abhishek.Kekane@nttdata.com</a>]
<br>
<b>Sent:</b> Monday, May 09, 2016 7:22 AM<br>
<b>To:</b> <a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators@lists.openstack.org</a><br>
<b>Subject:</b> [Openstack-operators] [Nova] Significance of Error Vs Failed status<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Hi All,<u></u><u></u></span></p>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">In Liberty release, we had upstream [1] a security fix to cleanup orphaned instance files from compute nodes for resize operation. To fix this security issue, a
new periodic task '_cleanup_incomplete_migrations’ was introduced that runs on each compute node which queries for deleted instances and migration status in “error” status. If there are any such instances, then it simply cleanup instance files on that particular
compute node.</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Similar issue is reported in LP bug [2] for Live-migration operation and we would like to use the same periodic task to fix this problem. But in case of live migration,
the migration status is set to “failed” instead of “error” status if migration fails for any reason. This change was introduced in patch [3] when migration object support was added for live migration. Due to this inconsistency, the periodic task will not pickup
instances to cleanup orphaned instance files. To fix this problem, we simply want to set the migration status to “error” in patch [4] same as done for resize operation to bring consistency to the code.</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">We have discussed about this issue in the nova meeting [5] and decided that to the client, migration status 'error' vs. 'failed' should be considered the same thing,
it's a failure. From operators point of view, is there any significance of setting migration status to 'error' or 'failed', if yes what is it and what impact it will have if migration status is changed from 'failed' to 'error'. Please provide your opinions
on the same.</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[1] <a href="https://review.openstack.org/#/c/219299" target="_blank">https://review.openstack.org/#/c/219299</a></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[2] : <a href="https://bugs.launchpad.net/nova/+bug/1470420" target="_blank">https://bugs.launchpad.net/nova/+bug/1470420</a></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[3] <a href="https://review.openstack.org/#/c/183331" target="_blank">https://review.openstack.org/#/c/183331</a></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[4] <a href="https://review.openstack.org/#/c/215483" target="_blank">https://review.openstack.org/#/c/215483</a></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<div style="margin-top:14.0pt;margin-bottom:14.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[5] <a href="http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2016-05-05.log.html#t2016-05-05T14:40:51" target="_blank">http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2016-05-05.log.html#t2016-05-05T14:40:51</a></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Thank You,<br>
<br>
Abhishek<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><br>
______________________________________________________________________<br>
Disclaimer: This email and any attachments are sent in strictest confidence<br>
for the sole use of the addressee and may contain legally privileged,<br>
confidential, and proprietary data. If you are not the intended recipient,<br>
please advise the sender by replying promptly to this email and then delete<br>
and destroy this email and any attachments without any further use, copying<br>
or forwarding.<u></u><u></u></p>
</div></div></div><div><div class="h5">
<br clear="both">
______________________________________________________________________<br>
Disclaimer: This email and any attachments are sent in strictest confidence<br>
for the sole use of the addressee and may contain legally privileged,<br>
confidential, and proprietary data. If you are not the intended recipient,<br>
please advise the sender by replying promptly to this email and then delete<br>
and destroy this email and any attachments without any further use, copying<br>
or forwarding.<br>
</div></div></div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>