Red Hat Bugzilla – Bug 1285782
JSON protocol should not be enabled on 3.5 host in 3.6 engine by default
Last modified: 2016-02-10 14:26:01 EST
Description of problem:
When adding host to 3.5 cluster in 3.6 engine, by default is JsonRPC enabled, however as it was not default in 3.5 engine as is default in 3.6 engine it should be for admin a possibility not mandatory.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add new host
2. See Advanced tab
Use JSON protocol is checked
Should be unchecked by default
As far as I know this is the default in 3.5 engine as well.
In 3.6 engine + 3.6 cluster, this is mandatory.
In 3.6 engine + 3.5 cluster, it should be the default.
I also think that even if it wasn't the default in 3.5 engine, it should be the default now. Moving to 3.6 cluster level will require you to have the communication to jsonrpc.
Is it really not the default to new 3.5 clusters in 3.5 engine?
Engine Cluster Status
3.5 3.4 Disabled
3.5 3.5 Enabled by deafult
3.6 3.5 Enabled by deafult
3.6 3.6 Mandatory
As you said this option is enabled by default on 3.5 as well.
If we want to push user to use JSON protocol pro-actively in 3.5 cluster this should be CLOSED as NOTABUG as it is intended design.
Always good to make sure this is indeed the behavior, especially when we want to get rid of xmlrpc in 4.0.
Closing as NOTABUG.