Description of problem: I'm using two host: one for the engine, the other as an hypervisor. Both with latest fedora 19 updates. I installed the ovirt engine, release 3.5 RC2, on the first host and from the web admin UI I was trying to add the second host without adding 3.5 repo on that. Version-Release number of selected component (if applicable): 3.5 RC2 How reproducible: 100% Steps to Reproduce: 1. two fedora 19 hosts, install the engine on one of them 2. Downgrade cluster level to 3.3 3. without adding any additional rpms repository on the second host try to add it via the web admin gui using jsonrpc Actual results: If I tray with jsonrpc the host goes into unassigned state without any details, with xmlrpc instead it shows: 'Host f19t12.localdomain is compatible with versions (3.0,3.1,3.2,3.3) and cannot join Cluster Default which is set to version 3.5.' Expected results: I got a detailed error message regarding cluster level as xmlrpc does. Additional info:
Can you please give more information what you mean in #3 in steps to reproduce? I do not understand what version you tried to add.
Please provide engine.log as well.
Please try with two fedora 19 hosts: 1. on the first one add oVirt 3.5 RC2 yum repository and install the engine as usual; it should create a Default datacenter with a default cluster with 3.5 compatibility level. 2. on the second host don't add oVirt 3.5 RC2 yum repository and just rely on packages from fedora 19 updates repository. 3. try to add the second host to the cluster both using jsonrpc or xmlrpc. Here my results: nw_1: fresh f19, no ovirt 3.5 repo, jsonrpc, failed with 'Host f19t14.localdomain installation failed. Network error during communication with the host.' nw_2: fresh f19, no ovirt 3.5 repo, xmlrpc, failed with 'Host f19t14.localdomain is compatible with versions (3.0,3.1,3.2,3.3) and cannot join Cluster Default which is set to version 3.5. xmlrpc correctly detects the cluster compatibility level, jsonrpc fails. I'm attaching my logs.
Created attachment 938938 [details] nw_1
Created attachment 938939 [details] nw_2
oVirt 3.5 has been released and should include the fix for this issue.