Back to bug 1373847
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-09-07 09:18:33 UTC | Flags | testing_ack? planning_ack? | |
| Oved Ourfali | 2016-09-15 05:37:03 UTC | Assignee | oourfali | masayag |
| Target Milestone | --- | ovirt-4.0.5 | ||
| Flags | ovirt-4.0.z? | |||
| Moti Asayag | 2016-09-19 10:50:01 UTC | CC | ahadas | |
| Flags | needinfo?(ahadas) | |||
| Moran Goldboim | 2016-09-20 08:03:15 UTC | CC | masayag, mgoldboi | |
| Flags | planning_ack? | needinfo?(masayag) planning_ack+ | ||
| Moti Asayag | 2016-09-20 11:51:57 UTC | Flags | needinfo?(ahadas) needinfo?(masayag) | |
| Moti Asayag | 2016-09-20 12:03:34 UTC | Flags | needinfo?(ahadas) | |
| Moran Goldboim | 2016-09-22 14:17:07 UTC | Priority | unspecified | high |
| Arik | 2016-09-25 07:18:41 UTC | Flags | needinfo?(ahadas) | |
| Pavel Stehlik | 2016-10-06 10:32:31 UTC | QA Contact | pstehlik | jbelka |
| Flags | testing_ack? | testing_ack+ | ||
| Moti Asayag | 2016-10-06 11:46:25 UTC | Status | NEW | ASSIGNED |
| Moti Asayag | 2016-10-09 13:09:42 UTC | Link ID | oVirt gerrit 65272 | |
| Status | ASSIGNED | POST | ||
| Red Hat Bugzilla Rules Engine | 2016-10-15 18:13:34 UTC | Link ID | oVirt gerrit 65276 | |
| Flags | ovirt-4.0.z? | ovirt-4.0.z+ | ||
| Sandro Bonazzola | 2016-10-20 06:20:21 UTC | Link ID | oVirt gerrit 65527 | |
| Status | POST | MODIFIED | ||
| Target Release | --- | 4.0.5.2 | ||
| Jiri Belka | 2016-10-24 12:08:26 UTC | Status | MODIFIED | ON_QA |
| Status | ON_QA | VERIFIED | ||
| Moti Asayag | 2016-10-25 07:15:35 UTC | Doc Text | Cause: Since 4.0, we support only hosts with 3.6 cluster compatibility and above. Therefore the only supported host protocol is JSON-RPC. Having hosts with XML RPC protocol are no longer supported. Consequence: Before the fix, the admin couldn't change the host protocol from XML RPC to JSON RPC without DB intervention. Fix: All hosts will be updated to JSON RPC. Result: Installing a host that doesn't support JSON RPC will end up with an installation failure. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Moti Asayag | 2016-10-25 08:43:38 UTC | CC | jbelka | |
| Doc Text | Cause: Since 4.0, we support only hosts with 3.6 cluster compatibility and above. Therefore the only supported host protocol is JSON-RPC. Having hosts with XML RPC protocol are no longer supported. Consequence: Before the fix, the admin couldn't change the host protocol from XML RPC to JSON RPC without DB intervention. Fix: All hosts will be updated to JSON RPC. Result: Installing a host that doesn't support JSON RPC will end up with an installation failure. | Cause: Since 4.0, we support only hosts with 3.6 cluster compatibility and above. Therefore the only supported host protocol is JSON-RPC. Having hosts with XML RPC protocol are no longer supported. Consequence: Before the fix, the admin couldn't change the host protocol from XML RPC to JSON RPC without DB intervention. Fix: All hosts will be updated to JSON RPC. Result: Installing a host that doesn't support JSON RPC will end up with an installation failure. An attempt to activate a host which doesn't support JSON RPC will end up in Non-responsive state of the host. | ||
| Flags | needinfo?(jbelka) | |||
| Jiri Belka | 2016-10-25 13:54:16 UTC | Flags | needinfo?(jbelka) | |
| Moti Asayag | 2016-10-25 14:26:51 UTC | Doc Text | Cause: Since 4.0, we support only hosts with 3.6 cluster compatibility and above. Therefore the only supported host protocol is JSON-RPC. Having hosts with XML RPC protocol are no longer supported. Consequence: Before the fix, the admin couldn't change the host protocol from XML RPC to JSON RPC without DB intervention. Fix: All hosts will be updated to JSON RPC. Result: Installing a host that doesn't support JSON RPC will end up with an installation failure. An attempt to activate a host which doesn't support JSON RPC will end up in Non-responsive state of the host. | Cause: Since 4.0, we support only hosts with 3.6 cluster compatibility and above. Therefore the only supported host protocol is JSON-RPC. Having hosts with XML RPC protocol are no longer supported. Consequence: Before the fix, the admin couldn't change the host protocol from XML RPC to JSON RPC without DB intervention. Fix: All hosts will be updated to JSON RPC. Result: Installing a host that doesn't support JSON RPC will end up with an installation failure. An attempt to activate a host which doesn't support JSON RPC (3.4 hosts and lower) will end up in Non-responsive state of the host. |
| Sandro Bonazzola | 2017-01-18 07:38:40 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2017-01-18 02:38:40 UTC |
Back to bug 1373847