Bug 1417835

Summary: vdsm vds.dispatcher ERROR SSL error receiving from <yajsonrpc.betterAsyncore.Dispatcher connected
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.InfraAssignee: Oved Ourfali <oourfali>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs, mperina, pkliczew
Target Milestone: ---   
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: 2017-01-31 14:19:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Logs none

Description Michael Burman 2017-01-31 08:52:29 UTC
Created attachment 1246115 [details]
Logs

Description of problem:
dsm vds.dispatcher ERROR SSL error receiving from <yajsonrpc.betterAsyncore.Dispatcher connected ('::ffff:10.35.160.148', 60238, 0, 0) at 0x2f90cb0>: unexpected eof

Which cause to failure in GetStatsVDS and to internal server error in engine.log

2017-01-31 10:29:24,244+02 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Internal server error 876 > 875

Version-Release number of selected component (if applicable):
4.1.0.3-0.1.el7

How reproducible:
100

Steps to Reproduce:
1. Run host on 4.1.0.3-0.1.el7

Actual results:
ERROR SSL error receiving from <yajsonrpc.betterAsyncore.Dispatcher connected ('::ffff:10.35.160.148', 60238, 0, 0) at 0x2f90cb0>: unexpected eof

In the event log ui we get - 
VDSM orchid-vds2.qa.lab.tlv.redhat.com command GetStatsVDS failed: 876 > 875

Failure in GetStatsVDS command and internal server error in engine.log

Comment 1 Oved Ourfali 2017-01-31 09:10:50 UTC
Piotr - a duplicate?

Comment 2 Piotr Kliczewski 2017-01-31 14:13:47 UTC
Yes, it is a duplicated of BZ #1412583

Comment 3 Martin Perina 2017-01-31 14:19:45 UTC

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