Back to bug 1325468
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-04-09 00:44:44 UTC | Flags | testing_ack? planning_ack? | |
| Sven Kieske | 2016-04-09 07:52:08 UTC | CC | s.kieske | |
| HWSD | 2016-04-09 10:41:15 UTC | CC | s.danzi | |
| Yaniv Kaul | 2016-04-10 07:39:02 UTC | Keywords | FutureFeature | |
| Red Hat Bugzilla | 2016-04-10 07:39:02 UTC | Doc Type | Bug Fix | Enhancement |
| Doron Fediuck | 2016-04-10 07:55:31 UTC | Keywords | Improvement | |
| CC | dfediuck | |||
| Flags | ovirt-future? | |||
| Yaniv Kaul | 2016-04-10 13:03:45 UTC | Summary | Autostart of VMs | [RFE] Autostart of VMs |
| David | 2016-04-12 06:29:46 UTC | CC | dmc | |
| Doron Fediuck | 2016-07-21 08:28:27 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=817363 | |
| Pat Riehecky | 2016-09-30 13:32:27 UTC | CC | riehecky | |
| Derek Atkins | 2016-10-18 18:20:00 UTC | CC | warlord | |
| Moran Goldboim | 2016-11-30 11:21:06 UTC | Priority | unspecified | high |
| CC | mgoldboi | |||
| Moran Goldboim | 2016-11-30 11:21:30 UTC | Target Milestone | --- | ovirt-4.2.0 |
| Flags | ovirt-4.2? | |||
| Martin Sivák | 2016-12-08 09:21:57 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1108678 | |
| Red Hat Bugzilla Rules Engine | 2016-12-27 16:38:14 UTC | Flags | ovirt-future? | |
| Benjamin Bellec | 2017-03-15 10:30:54 UTC | CC | b.bellec | |
| Justin Zygmont | 2017-04-26 08:08:58 UTC | CC | solarflow99 | |
| Yaniv Kaul | 2017-06-06 19:13:41 UTC | Assignee | sherold | mgoldboi |
| Flags | needinfo?(mgoldboi) | |||
| Martin Sivák | 2017-06-21 12:25:56 UTC | Depends On | 1463653 | |
| Moran Goldboim | 2017-07-02 18:28:46 UTC | Flags | needinfo?(mgoldboi) | |
| Yaniv Kaul | 2017-07-03 06:39:37 UTC | Flags | needinfo?(mgoldboi) | |
| Gil Klein | 2017-07-12 10:46:16 UTC | QA Contact | gklein | mavital |
| meital avital | 2017-08-21 10:07:36 UTC | QA Contact | mavital | alukiano |
| Doron Fediuck | 2017-09-03 10:21:13 UTC | Target Milestone | ovirt-4.2.0 | ovirt-4.3.0 |
| Flags | ovirt-4.2? | ovirt-4.3? | ||
| Martin Sivák | 2017-10-04 17:36:03 UTC | Flags | needinfo?(mgoldboi) | |
| Martin Sivák | 2017-10-04 17:37:15 UTC | Alias | autostart-w-engine | |
| Chris Adams | 2017-10-04 18:14:36 UTC | CC | linux | |
| Scott Walker | 2017-11-27 23:30:43 UTC | CC | crimson | |
| Klaas Demter | 2017-11-28 08:21:02 UTC | CC | klaas | |
| Michal Skrivanek | 2017-12-06 13:18:27 UTC | CC | michal.skrivanek | |
| Yaniv Kaul | 2018-02-11 11:31:46 UTC | Flags | needinfo?(mgoldboi) | |
| Moran Goldboim | 2018-02-27 10:58:15 UTC | Flags | needinfo?(mgoldboi) | |
| Yaniv Kaul | 2018-02-27 14:17:25 UTC | CC | msivak | |
| Flags | needinfo?(msivak) | |||
| Yaniv Kaul | 2018-02-27 14:32:06 UTC | Summary | [RFE] Autostart of VMs | [RFE] Autostart of VMs that are down (with Engine assistance - Engine has to be up) |
| Michal Skrivanek | 2018-02-27 19:34:16 UTC | Flags | needinfo?(mgoldboi) | |
| meital avital | 2018-03-07 12:54:12 UTC | CC | mavital | |
| QA Contact | alukiano | pagranat | ||
| Moran Goldboim | 2018-04-03 14:44:31 UTC | Flags | needinfo?(msivak) needinfo?(mgoldboi) | |
| Michal Skrivanek | 2018-04-03 14:49:45 UTC | Flags | needinfo?(msivak) | |
| Martin Sivák | 2018-04-03 15:09:07 UTC | Flags | needinfo?(msivak) | |
| Marian Jankular | 2018-07-20 10:17:22 UTC | CC | mjankula | |
| Marian Jankular | 2018-07-23 15:38:52 UTC | Blocks | 1607510 | |
| Ryan Barry | 2019-01-28 08:30:15 UTC | CC | rbarry | |
| Target Milestone | ovirt-4.3.0 | ovirt-4.4.0 | ||
| Flags | ovirt-4.3? | ovirt-4.4? | ||
| Michal Skrivanek | 2019-07-25 11:41:42 UTC | Comment 23 is private | 1 | 0 |
| Status | NEW | ASSIGNED | ||
| Assignee | mgoldboi | akrejcir | ||
| Ryan Barry | 2019-09-13 12:52:55 UTC | Status | ASSIGNED | POST |
| Link ID | oVirt gerrit 102522 | |||
| Link ID | oVirt gerrit 102785 | |||
| Link ID | oVirt gerrit 103233 | |||
| CC | Rhev-m-bugs | |||
| Component | RFEs | ovirt-engine | ||
| Version | future | 4.2.0 | ||
| Product | ovirt-engine | Red Hat Enterprise Virtualization Manager | ||
| Flags | ovirt-4.4? planning_ack? testing_ack? | |||
| Ryan Barry | 2019-09-13 12:54:54 UTC | Blocks | 1269908 | |
| Ryan Barry | 2019-09-13 12:55:41 UTC | CC | rhodain | |
| Link ID | Red Hat Knowledge Base (Solution) 2889011 | |||
| Ryan Barry | 2019-09-13 12:55:51 UTC | Blocks | 1269908 | |
| CC | pvilayat | |||
| Link ID | Red Hat Knowledge Base (Solution) 358303 | |||
| Jens Kuehnel | 2019-09-14 14:50:09 UTC | CC | bugzilla-redhat | |
| Ameya Charekar | 2019-09-26 07:38:10 UTC | CC | achareka | |
| Andrej Krejcir | 2019-10-01 11:05:13 UTC | Status | POST | MODIFIED |
| Frank DeLorey | 2019-10-24 11:41:16 UTC | CC | fdelorey | |
| Sandro Bonazzola | 2019-12-13 11:36:40 UTC | Status | MODIFIED | ON_QA |
| Martin Tessun | 2019-12-13 16:17:07 UTC | CC | mtessun | |
| Marina Kalinin | 2020-01-16 17:33:26 UTC | CC | mkalinin | |
| Blocks | 1670339 | |||
| Andrej Krejcir | 2020-01-17 11:05:31 UTC | Doc Text | There are two features in the RFE. 1. After a HA VM crashes, the engine will try to restart it indefinitely. At first with a short delay between restarts and after a specified amount of failed retries, the delay is longer. There are 3 new configuration options: - RetryToRunAutoStartVmShortIntervalInSeconds - Is the short delay. By default 30 seconds. - RetryToRunAutoStartVmLongIntervalInSeconds - Is the long delay. By default 30 minutes. - NumOfTriesToRunFailedAutoStartVmInShortIntervals - Is the number of failed retires with short delay. By default 10. 2. The crashed HA VMs are started in order according to their priority. The start of lower priority VMs is delayed until higher priority VMs are started and have 'Up' status. There is a new configuration option 'MaxTimeAutoStartBlockedOnPriority', that specifies the maximum time a VM can be delayed by the start of higher priority VMs. By default it is 10 minutes. |
|
| Peter Lauterbach | 2020-02-07 14:41:41 UTC | CC | pelauter | |
| Polina | 2020-02-10 11:33:33 UTC | Status | ON_QA | ASSIGNED |
| Polina | 2020-02-10 21:30:35 UTC | Depends On | 1463653 | 1801439 |
| Polina | 2020-02-17 12:26:07 UTC | Status | ASSIGNED | VERIFIED |
| Rolfe Dlugy-Hegwer | 2020-03-03 03:28:27 UTC | CC | akrejcir, rdlugyhe | |
| Doc Text | There are two features in the RFE. 1. After a HA VM crashes, the engine will try to restart it indefinitely. At first with a short delay between restarts and after a specified amount of failed retries, the delay is longer. There are 3 new configuration options: - RetryToRunAutoStartVmShortIntervalInSeconds - Is the short delay. By default 30 seconds. - RetryToRunAutoStartVmLongIntervalInSeconds - Is the long delay. By default 30 minutes. - NumOfTriesToRunFailedAutoStartVmInShortIntervals - Is the number of failed retires with short delay. By default 10. 2. The crashed HA VMs are started in order according to their priority. The start of lower priority VMs is delayed until higher priority VMs are started and have 'Up' status. There is a new configuration option 'MaxTimeAutoStartBlockedOnPriority', that specifies the maximum time a VM can be delayed by the start of higher priority VMs. By default it is 10 minutes. | 1. After a high-availability virtual machine (HA VM) crashes, the Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified amount of failed retries, the delay is longer. The current release adds three new configuration options: - RetryToRunAutoStartVmShortIntervalInSeconds - Is the short delay. (Default: 30 seconds) - RetryToRunAutoStartVmLongIntervalInSeconds - Is the long delay. (Default: 30 minutes) - NumOfTriesToRunFailedAutoStartVmInShortIntervals - Is the number of failed restarts with short delays. (Default: 10 retries) 2. The Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, 'MaxTimeAutoStartBlockedOnPriority,' which sets the maximum time the Manager waits before starting a lower-priority VM. (Default: 10 minutes) | ||
| Flags | needinfo?(akrejcir) | |||
| Andrej Krejcir | 2020-03-03 09:29:58 UTC | Flags | needinfo?(akrejcir) | |
| Jeff Fearn 🐞 | 2020-04-27 01:37:45 UTC | CC | Rhev-m-bugs | |
| PnT Account Manager | 2020-07-09 23:41:54 UTC | CC | rbarry | |
| Rolfe Dlugy-Hegwer | 2020-07-15 23:20:52 UTC | Doc Text | 1. After a high-availability virtual machine (HA VM) crashes, the Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified amount of failed retries, the delay is longer. The current release adds three new configuration options: - RetryToRunAutoStartVmShortIntervalInSeconds - Is the short delay. (Default: 30 seconds) - RetryToRunAutoStartVmLongIntervalInSeconds - Is the long delay. (Default: 30 minutes) - NumOfTriesToRunFailedAutoStartVmInShortIntervals - Is the number of failed restarts with short delays. (Default: 10 retries) 2. The Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, 'MaxTimeAutoStartBlockedOnPriority,' which sets the maximum time the Manager waits before starting a lower-priority VM. (Default: 10 minutes) | 1. After a high-availability virtual machine (HA VM) crashes, the Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified amount of failed retries, the delay is longer. The current release adds three new configuration options: * RetryToRunAutoStartVmShortIntervalInSeconds - Is the short delay. (Default: 30 seconds) * RetryToRunAutoStartVmLongIntervalInSeconds - Is the long delay. (Default: 30 minutes) * NumOfTriesToRunFailedAutoStartVmInShortIntervals - Is the number of failed restarts with short delays. (Default: 10 retries) 2. The Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, 'MaxTimeAutoStartBlockedOnPriority,' which sets the maximum time the Manager waits before starting a lower-priority VM. (Default: 10 minutes) |
| Rolfe Dlugy-Hegwer | 2020-07-29 23:52:47 UTC | Doc Text | 1. After a high-availability virtual machine (HA VM) crashes, the Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified amount of failed retries, the delay is longer. The current release adds three new configuration options: * RetryToRunAutoStartVmShortIntervalInSeconds - Is the short delay. (Default: 30 seconds) * RetryToRunAutoStartVmLongIntervalInSeconds - Is the long delay. (Default: 30 minutes) * NumOfTriesToRunFailedAutoStartVmInShortIntervals - Is the number of failed restarts with short delays. (Default: 10 retries) 2. The Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, 'MaxTimeAutoStartBlockedOnPriority,' which sets the maximum time the Manager waits before starting a lower-priority VM. (Default: 10 minutes) | With this enhancement: 1. After a high-availability virtual machine (HA VM) crashes, the Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified amount of failed retries, the delay is longer. The current release adds three new configuration options: * RetryToRunAutoStartVmShortIntervalInSeconds - Is the short delay. (Default: 30 seconds) * RetryToRunAutoStartVmLongIntervalInSeconds - Is the long delay. (Default: 30 minutes) * NumOfTriesToRunFailedAutoStartVmInShortIntervals - Is the number of failed restarts with short delays. (Default: 10 retries) 2. The Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, 'MaxTimeAutoStartBlockedOnPriority,' which sets the maximum time the Manager waits before starting a lower-priority VM. (Default: 10 minutes) |
| Rolfe Dlugy-Hegwer | 2020-07-30 21:37:36 UTC | Doc Text | With this enhancement: 1. After a high-availability virtual machine (HA VM) crashes, the Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified amount of failed retries, the delay is longer. The current release adds three new configuration options: * RetryToRunAutoStartVmShortIntervalInSeconds - Is the short delay. (Default: 30 seconds) * RetryToRunAutoStartVmLongIntervalInSeconds - Is the long delay. (Default: 30 minutes) * NumOfTriesToRunFailedAutoStartVmInShortIntervals - Is the number of failed restarts with short delays. (Default: 10 retries) 2. The Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, 'MaxTimeAutoStartBlockedOnPriority,' which sets the maximum time the Manager waits before starting a lower-priority VM. (Default: 10 minutes) | After a high-availability virtual machine (HA VM) crashes, the RHV Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified number of failed retries, the delay is longer. The current release adds three new configuration options: `RetryToRunAutoStartVmShortIntervalInSeconds` - Is the short delay. (Default: 30 seconds) + `RetryToRunAutoStartVmLongIntervalInSeconds` - Is the long delay. (Default: 30 minutes) + `NumOfTriesToRunFailedAutoStartVmInShortIntervals` - Is the number of failed restarts with short delays. (Default: 10 retries) The Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, 'MaxTimeAutoStartBlockedOnPriority,' which sets the maximum time the Manager waits before starting a lower-priority VM. (Default: 10 minutes) |
| Rolfe Dlugy-Hegwer | 2020-07-31 12:51:52 UTC | Doc Text | After a high-availability virtual machine (HA VM) crashes, the RHV Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified number of failed retries, the delay is longer. The current release adds three new configuration options: `RetryToRunAutoStartVmShortIntervalInSeconds` - Is the short delay. (Default: 30 seconds) + `RetryToRunAutoStartVmLongIntervalInSeconds` - Is the long delay. (Default: 30 minutes) + `NumOfTriesToRunFailedAutoStartVmInShortIntervals` - Is the number of failed restarts with short delays. (Default: 10 retries) The Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, 'MaxTimeAutoStartBlockedOnPriority,' which sets the maximum time the Manager waits before starting a lower-priority VM. (Default: 10 minutes) | After a high-availability virtual machine (HA VM) crashes, the RHV Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified number of failed retries, the delay is longer. + The current release adds three new configuration options: + * `RetryToRunAutoStartVmShortIntervalInSeconds` - Is the short delay, in seconds. (Default: `30`) * `RetryToRunAutoStartVmLongIntervalInSeconds` - Is the long delay, in seconds. (Default: `1800`, which equals 30 minutes) * `NumOfTriesToRunFailedAutoStartVmInShortIntervals` - Is the number of failed restarts with short delays. (Default: `10` tries) + Also, the Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, `MaxTimeAutoStartBlockedOnPriority`, which sets the maximum time, in minutes, that the Manager waits before starting a lower-priority VM. (Default: `10` minutes) |
| Rolfe Dlugy-Hegwer | 2020-07-31 13:13:33 UTC | Doc Text | After a high-availability virtual machine (HA VM) crashes, the RHV Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified number of failed retries, the delay is longer. + The current release adds three new configuration options: + * `RetryToRunAutoStartVmShortIntervalInSeconds` - Is the short delay, in seconds. (Default: `30`) * `RetryToRunAutoStartVmLongIntervalInSeconds` - Is the long delay, in seconds. (Default: `1800`, which equals 30 minutes) * `NumOfTriesToRunFailedAutoStartVmInShortIntervals` - Is the number of failed restarts with short delays. (Default: `10` tries) + Also, the Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds a new configuration option, `MaxTimeAutoStartBlockedOnPriority`, which sets the maximum time, in minutes, that the Manager waits before starting a lower-priority VM. (Default: `10` minutes) | After a high-availability virtual machine (HA VM) crashes, the RHV Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified number of failed retries, the delay is longer. + Also, the Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' + The current release adds new configuration options: + * `RetryToRunAutoStartVmShortIntervalInSeconds`, the short delay, in seconds. The default value is `30`. * `RetryToRunAutoStartVmLongIntervalInSeconds`, the long delay, in seconds. The default value is `1800`, which equals 30 minutes. * `NumOfTriesToRunFailedAutoStartVmInShortIntervals`, the number of restart tries with short delays before switching to long delays. The default value is `10` tries. * `MaxTimeAutoStartBlockedOnPriority`, the maximum time, in minutes, before starting a lower-priority VM. The default value is `10` minutes. |
| Rolfe Dlugy-Hegwer | 2020-07-31 16:07:05 UTC | Doc Text | After a high-availability virtual machine (HA VM) crashes, the RHV Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified number of failed retries, the delay is longer. + Also, the Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' + The current release adds new configuration options: + * `RetryToRunAutoStartVmShortIntervalInSeconds`, the short delay, in seconds. The default value is `30`. * `RetryToRunAutoStartVmLongIntervalInSeconds`, the long delay, in seconds. The default value is `1800`, which equals 30 minutes. * `NumOfTriesToRunFailedAutoStartVmInShortIntervals`, the number of restart tries with short delays before switching to long delays. The default value is `10` tries. * `MaxTimeAutoStartBlockedOnPriority`, the maximum time, in minutes, before starting a lower-priority VM. The default value is `10` minutes. | After a high-availability virtual machine (HA VM) crashes, the RHV Manager tries to restart it indefinitely. At first, with a short delay between restarts. After a specified number of failed retries, the delay is longer. Also, the Manager starts crashed HA VMs in order of priority, delaying lower-priority VMs until higher-priority VMs are 'Up.' The current release adds new configuration options: * `RetryToRunAutoStartVmShortIntervalInSeconds`, the short delay, in seconds. The default value is `30`. * `RetryToRunAutoStartVmLongIntervalInSeconds`, the long delay, in seconds. The default value is `1800`, which equals 30 minutes. * `NumOfTriesToRunFailedAutoStartVmInShortIntervals`, the number of restart tries with short delays before switching to long delays. The default value is `10` tries. * `MaxTimeAutoStartBlockedOnPriority`, the maximum time, in minutes, before starting a lower-priority VM. The default value is `10` minutes. |
| Lukas Svaty | 2020-08-03 15:30:20 UTC | Flags | testing_plan_complete- | |
| errata-xmlrpc | 2020-08-04 11:25:54 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2020-08-04 13:16:05 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2020-08-04 13:16:05 UTC | |||
| errata-xmlrpc | 2020-08-04 13:16:43 UTC | Link ID | Red Hat Product Errata RHSA-2020:3247 | |
| Red Hat One Jira (issues.redhat.com) | 2021-06-10 11:25:21 UTC | Link ID | Red Hat Issue Tracker RHV-36354 | |
| Rolfe Dlugy-Hegwer | 2021-06-10 12:40:16 UTC | CC | rdlugyhe |
Back to bug 1325468