Bug 1343112

Summary: The engine shows warning message when adds the additional host in the time of the HE deploy "Host hosted_engine_2 uses not compatible protocol during activation (xmlrpc instead of jsonrpc)"
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Artyom <alukiano>
Component: GeneralAssignee: Rafael Martins <rmartins>
Status: CLOSED DUPLICATE QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: low    
Version: 2.0.0CC: alukiano, bugs, dfediuck, nsednev, rgolan, stirabos
Target Milestone: ovirt-4.1.0-alphaFlags: dfediuck: ovirt-4.1?
rule-engine: planning_ack?
dfediuck: devel_ack+
rule-engine: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-14 14:06:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
bug logs(second host alma06.qa.lab.tlv.redhat.com) none

Description Artyom 2016-06-06 14:26:25 UTC 
Created attachment 1165219 [details]
bug logs(second host alma06.qa.lab.tlv.redhat.com)

Description of problem:
The engine shows warning message when adds the additional host in the time of the HE deploy.
2016-06-06 05:05:24,539 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-22) [52dae060] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Host hosted_engine_2 uses not compatible protocol during activation (xmlrpc instead of jsonrpc). Please examine installation logs and VDSM logs for failures and reinstall the host.

I do not sure if it is the really serious problem, but I know that we stop support xmlrpc under 4.0, and this can create some additional problems(like problems with the monitoring).

Also, I can not see some additional Traceback connect to this message under vdsm or host-deploy log.


Version-Release number of selected component (if applicable):
Hosts
=====
ovirt-hosted-engine-setup-2.0.0-1.el7ev.noarch
ovirt-hosted-engine-ha-2.0.0-1.el7ev.noarch
vdsm-4.18.1-11.gita92976e.el7ev.x86_64
Engine
======
rhevm-4.0.0.2-0.1.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run hosted-engine deploy on the first host
2. Run hosted-engine deploy on the second host
3. 

Actual results:
When I finish deployment of the second host I can see warning message under the engine.

Expected results:
No any error or warning messages under the engine

Additional info:
After I tried to start auto-import procedure, but it did not start(Roy said it because monitoring problem), I do not sure if it connects to warning message or to the bug https://bugzilla.redhat.com/show_bug.cgi?id=1343005
Comment 1 Doron Fediuck 2016-06-07 09:06:45 UTC 
Did the operation fail?
If not, there's no reason for making this a high severity bz.
Comment 2 Doron Fediuck 2016-06-07 09:45:51 UTC 
*** Bug 1343147 has been marked as a duplicate of this bug. ***
Comment 3 Artyom 2016-06-07 10:42:28 UTC 
No looks like action succeeds, but like I said under description:
"I do not sure if it is the really serious problem, but I know that we stop support xmlrpc under 4.0, and this can create some additional problems(like problems with the monitoring).", so I put it under high severity if you sure that it just some cosmetical issue you can decrease severity.
Comment 4 Nikolai Sednev 2016-06-07 11:23:38 UTC 
In my case additional hosted-engine-host was added, became active, and was seen via CLI's "hosted-engine --vm-status" command.
Comment 5 Doron Fediuck 2016-06-14 07:57:08 UTC 
Removed the blocked bzs as this is not an issue other than a general warning
which we'll remove later on if still relevant.
Comment 6 Simone Tiraboschi 2016-09-14 14:06:27 UTC 

*** This bug has been marked as a duplicate of bug 1101554 ***