<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi All,<br>
<br>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif" color="black"><font face="Arial">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.</font></font></div>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif">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. </font><font face="Arial">This</font><font face="Arial,sans-serif"> 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.</font></div>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif" color="black"><font face="Arial">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.</font></font></div>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif" color="black"> </font></div>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif" color="black"><font face="Arial">[1] </font><a href="https://review.openstack.org/#/c/219299" target="_blank"><font face="Arial">https://review.openstack.org/#/c/219299</font></a></font></div>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif" color="black"><font face="Arial">[2] : </font><a href="https://bugs.launchpad.net/nova/+bug/1470420" target="_blank"><font face="Arial">https://bugs.launchpad.net/nova/+bug/1470420</font></a></font></div>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif" color="black">[3] <a href="https://review.openstack.org/#/c/183331" target="_blank">https://review.openstack.org/#/c/183331</a></font></div>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif" color="black"><font face="Arial">[4] </font><a href="https://review.openstack.org/#/c/215483" target="_blank"><font face="Arial">https://review.openstack.org/#/c/215483</font></a></font></div>
<div style="margin-top:14pt;margin-bottom:14pt;"><font face="Arial,sans-serif" color="black"><font face="Arial">[5] </font><a href="http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2016-05-05.log.html#t2016-05-05T14:40:51" target="_blank"><font face="Arial">http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2016-05-05.log.html#t2016-05-05T14:40:51</font></a></font></div>
Thank You,<br>
<br>
Abhishek<br>
</div>
<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>
</body>
</html>