Bug 1309419

Summary: Overcloud cloud provider has exclamation mark in quadrant
Product: Red Hat Quickstart Cloud Installer Reporter: Thom Carlin <tcarlin>
Component: Installation - CloudFormsAssignee: Jason Montleon <jmontleo>
Status: CLOSED DEFERRED QA Contact: Tasos Papaioannou <tpapaioa>
Severity: medium Docs Contact: Dan Macpherson <dmacpher>
Priority: unspecified    
Version: 1.0CC: apagac, bthurber, jmatthew, jmontleo, tpapaioa
Target Milestone: TP3Keywords: Triaged
Target Release: 1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-25 17:28:55 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: 1315447    

Description Thom Carlin 2016-02-17 18:28:28 UTC 
Description of problem:

deployment-name-RHOS cloud provider has exclamation mark (!) in quadrant

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

TP2 RC9

How reproducible:

100%

Steps to Reproduce:
1. Install RHCI + TripleO ISO's
2. Log in to run launch-fusor*-installer
3. Deploy OpenStack + CloudForms
4. In CloudForms: Clouds > Providers

Actual results:

Exclamation mark

Expected results:

Green checkmark

Additional info:

Default security protocol is SSL without Validation.  Both "SSL without Validation" and "SSL" return "Credential validation was not successful: Socket error: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)"

Workaround: Non-SSL security protocol
Comment 1 Antonin Pagac 2016-02-18 10:53:33 UTC 
*** Bug 1309610 has been marked as a duplicate of this bug. ***
Comment 2 Antonin Pagac 2016-02-18 14:12:49 UTC 
Reproduced on RHELOSP+CFME installation, TP2 RC9
Comment 3 Jason Montleon 2016-03-18 19:19:50 UTC 
https://github.com/fusor/fusor/pull/726/files
Comment 4 Mike McCune 2016-03-28 22:47:43 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 5 John Matthews 2016-04-05 14:07:49 UTC 
In TP3 RC2
Comment 6 Tasos Papaioannou 2016-04-20 17:11:01 UTC 
Verified on TP3 (QCI-1.0-RHEL-7-20160411.t.0 + QCIOOO-7-RHEL-7-20160408.t.1).
Comment 7 Sudhir Mallamprabhakara 2019-02-25 17:28:55 UTC 
QCI has sunset. Closing the BZ's