Description of problem: [Condor non-SSL, Cumin SSL] - setup condor to not use /disable SSL SCHEDD.AVIARY_SSL = False SCHEDD.AVIARY_SSL_SERVER_CERT = /tmp/ssl/serv.pem SCHEDD.AVIARY_SSL_SERVER_KEY = /tmp/ssl/serv.pem SCHEDD.AVIARY_SSL_CA_DIR = /tmp/ssl SCHEDD.AVIARY_SSL_CA_FILE = /tmp/ssl/ca.pem QUERY_SERVER.AVIARY_SSL = False QUERY_SERVER.AVIARY_SSL_SERVER_CERT = /tmp/ssl/serv.pem QUERY_SERVER.AVIARY_SSL_SERVER_KEY = /tmp/ssl/serv.pem QUERY_SERVER.AVIARY_SSL_CA_DIR = /tmp/ssl QUERY_SERVER.AVIARY_SSL_CA_FILE = /tmp/ssl/ca.pem - enable SSL on cumin side - Start cumin and logfile shows that everything is OK: DEBUG AviaryOperations: suds logging on INFO AviaryOperations: using client and server certificate validation for ssl connections, solution is M2Crypto INFO AviaryOperations: verify server domain against certificate during validation (True) INFO Enabled Aviary interface for job submission and control. INFO Enabled Aviary interface for query operations. - try to submit job and it failed RHEL5 Submit job 'zzz': Failed (unexpected eof) RHEL6 Submit job 'zzz': Failed (Trouble reaching host (hostname), [Errno 8] _ssl.c:490: EOF occurred in violation of protocol) Version-Release number of selected component (if applicable): cumin-0.1.5098-2 How reproducible: 100% Steps to Reproduce: 1. Setup condor-aviary non-SSL 2. Setup cumin aviary-SSL 3. Try to use cumin Actual results: Cumin doesn't warn at startup that setup isn't usable. Expected results: Cumin warns at startup that setup isn't usable. Additional info:
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.