Bug 1253137 - Unable to create Orgs due to SSL issues with tomcat6 [NEEDINFO]
Unable to create Orgs due to SSL issues with tomcat6
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Organizations and Locations (Show other bugs)
All Linux
medium Severity medium (vote)
: GA
: 6.2
Assigned To: satellite6-bugs
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-08-13 01:48 EDT by Anand Vaddarapu
Modified: 2017-02-09 13:29 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-02-09 13:29:52 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
bkearney: needinfo? (avaddara)

Attachments (Terms of Use)

  None (edit)
Description Anand Vaddarapu 2015-08-13 01:48:37 EDT
Description of problem:
I get this error when I creating new Organization "There was an issue with the backend service candlepin: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: tlsv1 alert internal error"

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

How reproducible:
Upon creating Organizations.

Steps to Reproduce:

Actual results:
Fails to create an Org with above mentioned error,
solution provided in Additionla info section.

Expected results:
Should succeed in creation of Orgs.

Additional info:

Found a temporary solution.

a) remove all ciphers from /etc/tomcat6/server.xml

and added just ciphers="SSL_RSA_WITH_RC4_128_SHA"

b) restart tomcat6 server

This is could be a dirty workaround please suggest appropriate approach.

same issue reported in BZ https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1061721 also removing java-1.7.0-openjdk.x86_64 doesn't fix the issue.
Comment 2 Bryan Kearney 2015-08-14 11:20:58 EDT
Was this a clean install, or did you have other things installer prior to this? My question is, how did you get these extra ciphers on the
Comment 3 Michael Solberg 2015-08-17 14:14:23 EDT
I just also ran into this on a clean install of 6.1 on RHEL 6.  The workaround suggested above resolved the issue for me.
Comment 8 Bryan Kearney 2016-10-04 16:26:29 EDT
Per the case, this was resolved by restarting the backend tomcat. I am closing this out. If you are still seeing this issue, please feel free to re-open.
Comment 9 Bryan Kearney 2017-02-09 13:29:52 EST
I missed closing this, doing it now.

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