Bug 1260069

Summary: exconn socket error connecting to openstack using ssl ... add better logging
Product: Red Hat CloudForms Management Engine Reporter: Felix Dewaleyne <fdewaley>
Component: ProvidersAssignee: Ladislav Smola <lsmola>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.4.0CC: cpelland, fdewaley, jfrey, jhardy, jprause, obarenbo
Target Milestone: GAKeywords: ZStream
Target Release: 5.5.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1267351 (view as bug list) Environment:
Last Closed: 2015-11-19 10:15:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1267351    

Description Felix Dewaleyne 2015-09-04 11:13:03 UTC 
Description of problem:
exconn socket error connecting to openstack using ssl

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

How reproducible:
not reproduced

Steps to Reproduce:
this happens when adding one OpenStack (with Nuage version 6) cloud provider

Actual results:
exconn socket errors are raised :

[----] E, [2015-09-01T12:49:12.809744 #5179:66bea8] ERROR -- : excon.error     #<Excon::Errors::SocketError: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)>


Expected results:
connection establishes or a more helpful error message is raised.

Additional info:
research seems to point at this fix  in exconn : https://github.com/excon/excon/commit/57a05453d6cf4dbf1382709ed9d7740a24bf0d4e
Comment 1 Felix Dewaleyne 2015-09-04 11:15:43 UTC 
might have opened a clone to https://bugzilla.redhat.com/show_bug.cgi?id=1252413
Comment 5 Greg Blomquist 2015-11-17 14:08:13 UTC 
Ladas,

Looks like another dup of the SSL bug you're already working on.
Comment 6 Ladislav Smola 2015-11-19 10:15:43 UTC 

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