Back to bug 1301914
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-01-26 11:20:50 UTC | Target Release | --- | 8.0 |
| Raoul Scarazzini | 2016-01-26 11:23:13 UTC | CC | abeekhof, fdinitto, michele, rscarazz | |
| Eoghan Glynn | 2016-01-26 11:44:22 UTC | Status | NEW | ASSIGNED |
| Assignee | eglynn | sbauza | ||
| Eoghan Glynn | 2016-01-26 11:44:43 UTC | Link ID | OpenStack gerrit 250101 | |
| Sylvain Bauza | 2016-01-26 11:46:48 UTC | Link ID | Launchpad 1518200 | |
| Sylvain Bauza | 2016-01-26 12:04:49 UTC | Status | ASSIGNED | POST |
| Jon Schlueter | 2016-02-01 19:14:40 UTC | CC | jschluet | |
| Lee Yarwood | 2016-02-17 11:48:50 UTC | Status | POST | MODIFIED |
| CC | lyarwood | |||
| Fixed In Version | openstack-nova-12.0.1-5.el7ost | |||
| Jon Schlueter | 2016-02-19 12:25:29 UTC | Target Milestone | --- | ga |
| errata-xmlrpc | 2016-02-19 13:02:45 UTC | Status | MODIFIED | ON_QA |
| Jon Schlueter | 2016-02-19 13:23:51 UTC | Status | ON_QA | MODIFIED |
| errata-xmlrpc | 2016-02-19 20:04:24 UTC | Status | MODIFIED | ON_QA |
| nlevinki | 2016-02-21 08:27:59 UTC | QA Contact | nlevinki | panbalag |
| Prasanth Anbalagan | 2016-03-08 19:20:15 UTC | QA Contact | panbalag | jhakimra |
| Sylvain Bauza | 2016-03-16 13:07:29 UTC | Doc Text | Cause: When a source compute node is back up, instances that have been successfully evacuated from it when the node was down are not deleted. Consequence: In case you want to evacuate instances back to the source compute node, having those not deleted makes the evacuate impossible for those instances. Fix: The successful migration status when evacuating an instance is now also verified for knowing which instances to delete when a compute node is back up. Result: Instances can be evacuated from one host to another, regardless of their previous locations. |
|
| Deepti Navale | 2016-03-30 03:11:45 UTC | CC | dnavale | |
| Doc Text | Cause: When a source compute node is back up, instances that have been successfully evacuated from it when the node was down are not deleted. Consequence: In case you want to evacuate instances back to the source compute node, having those not deleted makes the evacuate impossible for those instances. Fix: The successful migration status when evacuating an instance is now also verified for knowing which instances to delete when a compute node is back up. Result: Instances can be evacuated from one host to another, regardless of their previous locations. | Previously, when a source compute node is back up after a migration, instances that have been successfully evacuated from it when the node was down were not deleted. A result of having the non-deleted instances makes it impossible to evacuate them. With this update, the successful migration status when evacuating an instance is now verified for knowing which instance to delete when a compute node is back up and running again. As a result, instances can be evacuated from one host to another, regardless of their previous locations. |
||
| errata-xmlrpc | 2016-04-07 21:26:04 UTC | Status | ON_QA | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-04-07 17:26:04 UTC | |||
| Russell Bryant | 2019-09-09 15:37:12 UTC | CC | rbryant |
Back to bug 1301914