Bug 1335207 - vdsmfake unable to communicate with ovirt-engine results in "Unrecognized message received"
Summary: vdsmfake unable to communicate with ovirt-engine results in "Unrecognized mes...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: vdsm-jsonrpc-java
Classification: oVirt
Component: General
Version: 1.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Piotr Kliczewski
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-11 15:03 UTC by mlehrer
Modified: 2016-05-16 15:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-16 15:05:16 UTC
oVirt Team: Infra
Embargoed:
gklein: ovirt-3.6.z?
rule-engine: blocker?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
engine log with debug (1.06 MB, application/zip)
2016-05-16 08:34 UTC, mlehrer
no flags Details
catilna out on vdsmfake (339.99 KB, text/plain)
2016-05-16 10:19 UTC, mlehrer
no flags Details

Description mlehrer 2016-05-11 15:03:09 UTC
Description of problem:
Unable to add fake host via VDSMFake.  After attempting to add fake host, fake host is marked unresponsive and can't communicate with ovirt-engine due to latest changes in jsonrpc​ ​on engine/vdsm.  The logs show the following exception:

2016-05-11 14:55:44,008 DEBUG [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Unrecognized message received 
        at org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message.parse(Message.java:204) [vdsm-jsonrpc-java-client.jar:]
        at org.ovirt.vdsm.jsonrpc.client.reactors.stomp.StompCommonClient.getMessage(StompCommonClient.java:157) [vdsm-jsonrpc-java-client.jar:]
        at org.ovirt.vdsm.jsonrpc.client.reactors.stomp.StompCommonClient.processIncoming(StompCommonClient.java:109) [vdsm-jsonrpc-java-client.jar:]
        at org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient.process(ReactorClient.java:204) [vdsm-jsonrpc-java-client.jar:]
        at org.ovirt.vdsm.jsonrpc.client.reactors.SSLClient.process(SSLClient.java:125) [vdsm-jsonrpc-java-client.jar:]
        at org.ovirt.vdsm.jsonrpc.client.reactors.Reactor.processChannels(Reactor.java:89) [vdsm-jsonrpc-java-client.jar:]
        at org.ovirt.vdsm.jsonrpc.client.reactors.Reactor.run(Reactor.java:65) [vdsm-jsonrpc-java-client.jar:]

2016-05-11 14:55:44,009 DEBUG [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) [] Message received: {"jsonrpc":"2.0","error":{"message":"Unrecognized message received ","code":"scale-3.fake.com:926031703"},"id":null}



Version-Release number of selected component (if applicable):
ovirt-engine 3.6.6


How reproducible:
very

Steps to Reproduce:
1.Set up vdsmfake
2.either use ssl or no ssl setup
3.add fake host

Actual results:
Host marked non-responsive

Expected results:
Fake Host to be added and active via vdsmfake simulator

Additional info:
VDSMfake is needed for scale testing.

Comment 1 Martin Perina 2016-05-12 08:06:30 UTC
Just small correction, this is not a bug in vdsm-jsonrpc-java, but in ovirt-vdsmfake. Unfortunately we don't have a product for ovirt-vdsmfake and the bug is related to jsonrpc communication, let's have it assigned to vdsm-jsonrpc-java for now.

Comment 2 Red Hat Bugzilla Rules Engine 2016-05-15 10:41:40 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Piotr Kliczewski 2016-05-16 07:09:37 UTC
Please provide engine log with debug log level set.

Comment 4 mlehrer 2016-05-16 08:34:48 UTC
Created attachment 1157806 [details]
engine log with debug

Comment 5 Piotr Kliczewski 2016-05-16 09:44:32 UTC
Please provide fakevdsm logs as well.

Comment 6 mlehrer 2016-05-16 10:19:40 UTC
Created attachment 1157830 [details]
catilna out on vdsmfake

Comment 7 Piotr Kliczewski 2016-05-16 15:05:16 UTC
After spending some time to investigate the issue we found that vdsmfake that there was port conflict and jsonrpc responds with:

2016-05-16 14:21:42,134 DEBUG [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (Stomp Reactor) [] HTTP/1.1 400 Bad Request
Server: Apache-Coyote/1.1
Transfer-Encoding: chunked
Date: Mon, 16 May 2016 13:08:12 GMT
Connection: close

after changing port configuration and restarting both vdsmfake and engine the communication started to work again.

As lessons learned from this bug we need to update vdsmfake documentation because it is not clear and it led to confusion.


Note You need to log in before you can comment on or make changes to this bug.