Back to bug 1390252
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-10-31 14:55:00 UTC | Flags | testing_ack? planning_ack? | |
| Martin Sivák | 2016-10-31 15:47:08 UTC | CC | mshira | |
| Flags | needinfo?(mshira) | |||
| Shira Maximov | 2016-10-31 16:17:08 UTC | Flags | needinfo?(mshira) | |
| Martin Sivák | 2016-11-01 08:35:16 UTC | Flags | needinfo?(mshira) | |
| Shira Maximov | 2016-11-01 08:47:28 UTC | Flags | needinfo?(mshira) | |
| Moran Goldboim | 2016-11-02 11:25:17 UTC | Priority | unspecified | urgent |
| CC | mgoldboi | |||
| Moran Goldboim | 2016-11-02 11:25:45 UTC | Flags | planning_ack? | planning_ack+ |
| Moran Goldboim | 2016-11-02 11:28:49 UTC | Target Milestone | --- | ovirt-4.0.5 |
| Flags | ovirt-4.0.z? ovirt-4.1.0? | |||
| Martin Sivák | 2016-11-02 13:11:43 UTC | Status | NEW | ASSIGNED |
| Assignee | bugs | msivak | ||
| Summary | after preforming "Start optimize", the vm still appears in 'VMS THAT SHOULD BE STARTED' and in 'MIGRATION / START STEPS' | The optimizer result is not updating according to the engine status | ||
| Martin Sivák | 2016-11-03 15:30:37 UTC | Link ID | oVirt gerrit 66033 | |
| Priority | urgent | high | ||
| Martin Sivák | 2016-11-04 12:03:16 UTC | Status | ASSIGNED | MODIFIED |
| Target Release | --- | 0.14 | ||
| Fixed In Version | ovirt-optimizer-0.14 | |||
| Martin Sivák | 2016-11-04 12:05:02 UTC | Doc Text | Cause: The oVirt SDKv4 can throw an error when the engine is not available or the login fails. The error was not properly handled. Consequence: The refresh threads died. Fix: The error is not properly handled (logged). Result: The optimizer refresh thread continues in degraded mode (no v4 features) and without a crash. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| meital avital | 2016-11-09 11:10:39 UTC | CC | mavital | |
| Flags | testing_ack? | testing_ack+ | ||
| Red Hat Bugzilla Rules Engine | 2016-11-09 11:10:43 UTC | Flags | ovirt-4.0.z? ovirt-4.1? | ovirt-4.0.z+ ovirt-4.1+ |
| Martin Sivák | 2016-11-14 10:25:18 UTC | Doc Text | Cause: The oVirt SDKv4 can throw an error when the engine is not available or the login fails. The error was not properly handled. Consequence: The refresh threads died. Fix: The error is not properly handled (logged). Result: The optimizer refresh thread continues in degraded mode (no v4 features) and without a crash. | Cause: The oVirt SDKv4 can throw an error when the engine is not available or the login fails. The error was not properly handled. This could happen when the engine was restarted for example. Workaround: All is fine again when the optimizer is restarted. Consequence: The refresh threads died. Fix: The error is now properly handled (and logged). Result: The optimizer refresh thread continues in degraded mode (no v4 features) and without a crash when the SDK v4 returns an error. |
| Doc Type | Bug Fix | Known Issue | ||
| Martin Sivák | 2016-11-21 15:47:19 UTC | Blocks | 1397100 | |
| Martin Sivák | 2016-11-21 16:05:38 UTC | Status | MODIFIED | ON_QA |
| Target Milestone | ovirt-4.0.5 | ovirt-4.0.6 | ||
| Doc Type | Known Issue | Bug Fix | ||
| Shira Maximov | 2016-11-28 08:37:30 UTC | Status | ON_QA | VERIFIED |
| Sandro Bonazzola | 2017-01-18 07:25:19 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2017-01-18 02:25:19 UTC |
Back to bug 1390252