Created attachment 1244372 [details]
Vdsm log from giediprime
Description of problem:
Adding hosts to RHV-M 4.1 brings up hosts in the Non-operational state. I have seen this twice, where I first put them in maintenance, then activated them and the second time where I just reactivated them from the RHV-M menu. These were completely newly installed environments, both times.
The error in the VDSM log on the host shows this:
2017-01-25 13:37:18,050 ERROR (JsonRpc (StompReactor)) [vds.dispatcher] SSL error receiving from <yajsonrpc.betterAsyncore.Dispatcher connected ('::ffff:10.19.168.41', 51934, 0, 0) at 0x23b25a8>: (104, 'Connection reset by peer') (betterAsyncore:113)
I will attach the VDSM and Host deploy logs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install 7.3 for Engine and Hosts
2. Install RHV 4.1
3. Add new hosts
Created attachment 1244373 [details]
Host deploy log of giediprime
Created attachment 1244374 [details]
First install of activating host from maintenance mode
Created attachment 1244375 [details]
Second install of activating host from non-operational mode
Please also attach engine.log.
Also, supervdsm.log, as we need to see the setupNetworks result.
Created attachment 1244395 [details]
Created attachment 1244396 [details]
Absolutely. I will reinstall the engine and after I file another, different bug.
Thanks. Please also specify what's the vdsm-jsonrpc-java version you're using, to make sure it is the right one.
Can you please try with 1.3.8?
I can do that.
Is that only in brew and not in the build?
This fix does work but would like to verify with RHV-M build that has the new vdsm-jsonrpc-java build.
new added hosts started in Up mode
hosts with vdsm-126.96.36.199-1.el7ev.x86_64 and vdsm-4.19.2-2.el7ev.x86_64
verified in ovirt-engine-188.8.131.52-0.1.el7.noarch