Bug 1468991 - Connection exception when trying to connect to the vdsm client
Summary: Connection exception when trying to connect to the vdsm client
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.19.20
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.1.4
: 4.19.22
Assignee: Piotr Kliczewski
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-10 08:04 UTC by Nelly Credi
Modified: 2019-04-28 14:04 UTC (History)
5 users (show)

Fixed In Version: 4.19.22
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-28 14:09:50 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: blocker+
lsvaty: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 79194 0 ovirt-4.1 MERGED ssl: wrong protocol used by the client 2020-11-02 03:36:36 UTC

Description Nelly Credi 2017-07-10 08:04:43 UTC
Description of problem:
There is an connection exception when trying to connect to vdsm client 

Version-Release number of selected component (if applicable):
4.19.21

How reproducible:
100%

Steps to Reproduce:
1.execute on the hosts: python -c "from vdsm import client;client.connect('localhost', 54321,
use_tls=True)"
2.
3.

Actual results:
connect fails
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/vdsm/client.py", line 121, in connect
    raise ConnectionError(host, port, use_tls, timeout, e)
vdsm.client.ConnectionError: Connection to localhost:54321 with use_tls=True, timeout=60 failed: an integer is required

Expected results:
we should be able to connect

Additional info:

Comment 1 Lukas Svaty 2017-07-19 15:14:20 UTC
verified in vdsm-4.19.22-1.el7ev.x86_64

[root@moonmoon ~]$ python -c "from vdsm import client;client.connect('localhost', 54321, use_tls=True)"

ergo success


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