Bug 1222958
Summary: | EMS Refresh against RHOS provider with self-signed certificate results in error | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Thom Carlin <tcarlin> |
Component: | Documentation | Assignee: | Andrew Dahms <adahms> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Thom Carlin <tcarlin> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 5.5.0 | CC: | gblomqui, jfrey, jhardy, mfeifer, obarenbo, tcarlin |
Target Milestone: | GA | Keywords: | Reopened |
Target Release: | 5.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
When an OpenStack provider is set up with services behind SSL termination, and a Red Hat CloudForms appliance is configured to communicate to the Keystone SSL endpoint, users may see the following error in the evm.log (and fog.log):
#<Excon::Errors::SocketError: end of file reached (EOFError)>
This error occurs because Red Hat CloudForms tries both non-SSL and SSL connections when getting the Keystone security token. This is a benign known issue and is scheduled to be addressed in a future version.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-24 01:44:32 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: |
Description
Thom Carlin
2015-05-19 13:40:35 UTC
Thom, I believe you used the default port 5000 for that environment. Try using port 5443 and I believe you will have better results. We see "ERROR -- : excon.error #<Excon::Errors::SocketError: end of file reached (EOFError)>" as part of the normal SSL/non-SSL process appearing in the logs. Worth a mention in the documentation somewhere... This known issue has been documented in the Release Notes document for Red Hat CloudForms 3.2 Closing. |