Bug #6817
jobsub_submit fails with misleading error message when port number is not specified
100%
Description
When user doesn't specify the port number in the jobsub server url, jobsub_submit fails with misleading error message indicating the server certificate verification failed.
<novagpvm01> jobsub_submit.py --debug --jobsub-server https://fifebatch-preprod.fnal.gov --resource-provides=usage_model=FERMICLOUD --OS=SL5,SL6 --group nova file:///afs/fnal.gov/files/home/room3/neha/testjob.sh
SERVER_ARGS: ['--resource-provides=usage_model=FERMICLOUD', '--OS=SL5,SL6', 'file:///afs/fnal.gov/files/home/room3/neha/testjob.sh']
CLIENT_ARGS: {'help': False, 'acctRole': None, 'debug': True, 'dropboxServer': None, 'acctGroup': 'nova', 'jobsubServer': 'https://fifebatch-preprod.fnal.gov'}
URL : https://fifebatch-preprod.fnal.gov/jobsub/acctgroups/nova/jobs/ LS1yZXNvdXJjZS1wcm92aWRlcz11c2FnZV9tb2RlbD1GRVJNSUNMT1VEIC0tT1M9U0w1LFNMNiBAL2Fmcy9mbmFsLmdvdi9maWxlcy9ob21lL3Jvb20zL25laGEvdGVzdGpvYi5zaA==
CREDENTIALS : {'key': '/tmp/jobsub_x509up_u60158', 'env_key': '/tmp/jobsub_x509up_u60158', 'cert': '/tmp/jobsub_x509up_u60158', 'env_cert': '/tmp/jobsub_x509up_u60158'}
SUBMIT_URL : https://fifebatch-preprod.fnal.gov/jobsub/acctgroups/nova/jobs/
SERVER_ARGS_B64: --resource-provides=usage_model=FERMICLOUD --OS=SL5,SL6 @/afs/fnal.gov/files/home/room3/neha/testjob.sh
Using CA_DIR: /etc/grid-security/certificates
Traceback (most recent call last):
File "/grid/fermiapp/products/common/prd/jobsub_client/v0_4/NULL/jobsubClient.py", line 211, in submit
curl.perform()
error: (60, 'SSL certificate problem, verify that the CA cert is OK. Details:\nerror:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed')
PyCurl Error 60: SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
<novagpvm01>
The server certificate is infact valid.
History
#1 Updated by Dennis Box over 6 years ago
This is a re-emergence of #6366. I don't yet understand why this is happening, the code to catch curl error 60 did not get deleted, its following a different execution path.
Dennis
#2 Updated by Dennis Box over 6 years ago
- Target version set to v1.0
#3 Updated by Dennis Box over 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
forgot to close this earlier
#4 Updated by Parag Mhashilkar over 6 years ago
- Assignee set to Dennis Box
#5 Updated by Parag Mhashilkar over 6 years ago
- Status changed from Resolved to Closed