Back to bug 1520424
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2017-12-04 13:13:53 UTC | Keywords | FutureFeature | |
| Martin Perina | 2017-12-04 13:34:43 UTC | Blocks | 1506217 | |
| Martin Perina | 2017-12-04 13:36:25 UTC | CC | mperina | |
| Assignee | mperina | emesika | ||
| Pavel Stehlik | 2017-12-06 09:19:47 UTC | QA Contact | pstehlik | pmatyas |
| Flags | testing_ack? | testing_ack+ | ||
| Petr Matyáš | 2017-12-15 14:23:10 UTC | Flags | testing_plan_complete- | |
| Oved Ourfali | 2018-01-04 09:51:00 UTC | CC | oourfali | |
| Martin Perina | 2018-01-04 12:08:07 UTC | CC | mgoldboi | |
| Eli Mesika | 2018-01-30 11:50:37 UTC | Status | NEW | ASSIGNED |
| Eli Mesika | 2018-02-07 09:26:33 UTC | Status | ASSIGNED | POST |
| Link ID | oVirt gerrit 87182 | |||
| Doc Text | Feature: After the start-up quite time, the engine will check for any non-responding hosts and if it find any, it will try to fence them. Reason: When engine is starting up , it ignores any non-responding hosts for a configurable quite time (5 minutes by default) in order to prevent "fencing-storm". The problem is that hosts that remain non-responding after this quite time are not fenced automatically and the administrator should fence them manually. Result: Hosts that were non-responsive and remain as such after the quite time and have power management will be fenced automatically | |||
| Doc Type | If docs needed, set a value | Enhancement | ||
| Lev Veyde | 2018-02-15 10:58:17 UTC | Link ID | oVirt gerrit 87564 | |
| Status | POST | MODIFIED | ||
| Status | MODIFIED | ON_QA | ||
| CC | lveyde | |||
| Fixed In Version | ovirt-engine-4.2.2 | |||
| Petr Matyáš | 2018-02-19 16:04:23 UTC | Status | ON_QA | VERIFIED |
| Marina Kalinin | 2018-02-19 21:16:20 UTC | CC | mkalinin | |
| Doc Text | Feature: After the start-up quite time, the engine will check for any non-responding hosts and if it find any, it will try to fence them. Reason: When engine is starting up , it ignores any non-responding hosts for a configurable quite time (5 minutes by default) in order to prevent "fencing-storm". The problem is that hosts that remain non-responding after this quite time are not fenced automatically and the administrator should fence them manually. Result: Hosts that were non-responsive and remain as such after the quite time and have power management will be fenced automatically | Feature: After the start-up quiet time, the engine will check for any non-responding hosts and if it find any, it will try to fence them. Reason: When engine is starting up , it ignores any non-responding hosts for a configurable quite time (5 minutes by default) in order to prevent "fencing-storm". The problem is that hosts that remain non-responding after this quiet time are not fenced automatically and the administrator should fence them manually. Result: Hosts that were non-responsive and remain as such after the quiet time and have power management will be fenced automatically |
||
| Byron Gravenorst | 2018-02-28 00:18:10 UTC | CC | bgraveno | |
| Doc Text | Feature: After the start-up quiet time, the engine will check for any non-responding hosts and if it find any, it will try to fence them. Reason: When engine is starting up , it ignores any non-responding hosts for a configurable quite time (5 minutes by default) in order to prevent "fencing-storm". The problem is that hosts that remain non-responding after this quiet time are not fenced automatically and the administrator should fence them manually. Result: Hosts that were non-responsive and remain as such after the quiet time and have power management will be fenced automatically | After starting up, the Manager will automatically attempt to fence unresponsive hosts that have power management enabled after the configurable quiet time (5 minutes by default) has elapsed. Previously the user needed to fence them manually. | ||
| Byron Gravenorst | 2018-02-28 01:45:49 UTC | Blocks | 1549899 | |
| Sandro Bonazzola | 2018-03-02 14:38:15 UTC | Target Release | --- | 4.2.2 |
| Sandro Bonazzola | 2018-03-29 11:16:36 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2018-03-29 07:16:36 UTC | |||
| Koutuk Shukla | 2018-07-25 14:42:08 UTC | CC | kshukla | |
| Link ID | Red Hat Knowledge Base (Solution) 3345741 | |||
| Koutuk Shukla | 2018-07-31 17:13:02 UTC | Link ID | Red Hat Knowledge Base (Solution) 3345741 | |
| Red Hat One Jira (issues.redhat.com) | 2022-03-13 15:13:36 UTC | Link ID | Red Hat Issue Tracker RHV-45187 |
Back to bug 1520424