Bug 1412550

Summary: Fix certificate validation for engine <-> VDSM encrypted connection when IPv6 is configured
Product: [oVirt] vdsm Reporter: Martin Perina <mperina>
Component: Bindings-APIAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Belka <jbelka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.20.0CC: bugs, gklein
Target Milestone: ovirt-4.1.1Flags: rule-engine: ovirt-4.1+
rule-engine: planning_ack+
mperina: devel_ack+
pstehlik: testing_ack+
Target Release: 4.19.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-21 09:32:39 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:
Bug Depends On:    
Bug Blocks: 1408847    

Description Martin Perina 2017-01-12 09:35:21 UTC 
Description of problem:

When we compare client name during establishing a secured connection between engine and VDSM, we don't properly handle IPv6 addresses.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Martin Perina 2017-01-18 08:58:34 UTC 
Missed RC build, moving to 4.1.1
Comment 2 Jiri Belka 2017-03-06 15:41:19 UTC 
ok, vdsm-4.19.7-1.el7ev.x86_64

communication via ipv6 on the host internally

# for i in 0 localhost `hostname`; do vdsClient -s $i getVdsCaps 2>&1 | grep software_version ; done
        software_version = '4.19'
        software_version = '4.19'
        software_version = '4.19'