Back to bug 1030367
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Pavel Stehlik | 2013-11-15 08:04:31 UTC | Depends On | 966503 | |
| Link ID | Red Hat Knowledge Base (Solution) 380273 | |||
| Link ID | oVirt gerrit 17942 | |||
| QA Contact | jbelka | mavital | ||
| meital avital | 2013-11-20 13:33:31 UTC | QA Contact | mavital | istein |
| Michal Skrivanek | 2014-02-03 15:37:14 UTC | Target Release | 3.3.1 | 3.3.2 |
| Roy Golan | 2014-02-13 13:43:57 UTC | Status | NEW | POST |
| Link ID | oVirt gerrit 20899 | |||
| Itamar Heim | 2014-02-23 09:15:45 UTC | Group | redhat | |
| Michal Skrivanek | 2014-02-24 14:41:51 UTC | Status | POST | MODIFIED |
| errata-xmlrpc | 2014-03-13 08:36:17 UTC | Status | MODIFIED | ON_QA |
| meital avital | 2014-03-19 12:07:31 UTC | Fixed In Version | is35 | |
| CC | mavital | |||
| QA Contact | istein | alukiano | ||
| Artyom | 2014-03-20 13:15:19 UTC | Status | ON_QA | VERIFIED |
| Zac Dover | 2014-04-03 02:26:00 UTC | Flags | needinfo?(rgolan) | |
| Roy Golan | 2014-04-07 10:42:33 UTC | Doc Text | Cause: when we move a host to maintenance we first migrate all "UP" VMs. this does not include VM in "MigratingTo" status as they are not still running under this host. after the attempt to migrate the VMs we try to put it to maintenance but fail because there are incomming Vms which soon be UP - thats a desirable protection. Consequence: the host will not move to maintenance unless be manually activated again. Fix: 1. cancel ongoing migrations to the host 2. attempt every configurable time interval (5 mins default) to put the host to maintenance again. Result: even if there are ongoing migration the host will cancel them and they will continue to run on their original SRC. after 5 minutes of the first status change to "PreparingForMaintenance" the host should try to maintenance again and should succeed if there are no VMs. | |
| Flags | needinfo?(rgolan) | |||
| Lucy Bopf | 2014-04-08 06:27:42 UTC | CC | lbopf | |
| Doc Text | Cause: when we move a host to maintenance we first migrate all "UP" VMs. this does not include VM in "MigratingTo" status as they are not still running under this host. after the attempt to migrate the VMs we try to put it to maintenance but fail because there are incomming Vms which soon be UP - thats a desirable protection. Consequence: the host will not move to maintenance unless be manually activated again. Fix: 1. cancel ongoing migrations to the host 2. attempt every configurable time interval (5 mins default) to put the host to maintenance again. Result: even if there are ongoing migration the host will cancel them and they will continue to run on their original SRC. after 5 minutes of the first status change to "PreparingForMaintenance" the host should try to maintenance again and should succeed if there are no VMs. | Previously, attempting to move a host into maintenance mode resulted in a static "Preparing for maintenance" status because virtual machines on that host with a "Migrating to" status were unable to be migrated elsewhere. Now, ongoing migrations to the chosen host are cancelled when maintenance mode is selected on that host, and the host will reattempt to enter maintenance mode after a period of five minutes. | ||
| errata-xmlrpc | 2014-04-09 17:02:19 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2014-04-09 17:53:13 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-04-09 13:53:13 UTC |
Back to bug 1030367