[jira] [Created] (AMBARI-21012) Livy service check fails with wire encryption setup

["Yesha Vora (JIRA)" <ji...@apache.org>]

Yesha Vora created AMBARI-21012:
-----------------------------------

             Summary: Livy service check fails with wire encryption setup
                 Key: AMBARI-21012
                 URL: https://issues.apache.org/jira/browse/AMBARI-21012
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 2.5.1
            Reporter: Yesha Vora


Livy service check fails after enabling Wire encryption.  This issue exist for Livy_server and Livy2_server both.
STR:
1) Set up below properties in livy.conf to enable WE.
{code}
livy.ssl.trustStore <Truststore File>
livy.ssl.trustStorePassword <Trustore passwd>
livy.key-password <keypassword>
livy.keystore <keystore file>
livy.keystore.password <keystore passwd>{code}
2) Run Spark Service check.

Spark service check with fail to validate Livy. It is using http port to connect to livy. When Wire encryption is enabled, it should use https protocol to connect to livy. 
{code:title=stderr}
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py", line 62, in <module>
    SparkServiceCheck().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 322, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py", line 59, in service_check
    raise Fail(format("Connection to all Livy servers failed"))
resource_management.core.exceptions.Fail: Connection to all Livy servers failed{code}
{code:title=stdout}
2017-05-12 21:21:08,531 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf
2017-05-12 21:21:08,551 - Execute['kinit -kt /etc/security/keytabs/xxx.headless.keytab xxx@XXX; '] {'user': 'spark'}
2017-05-12 21:21:08,683 - Execute['kinit -kt /etc/security/keytabs/smokeuser.headless.keytab xxx@XXX; '] {'user': 'livy'}
2017-05-12 21:21:08,809 - Execute['curl -s -o /dev/null -w'%{http_code}' --negotiate -u: -k https://xxxx:18481 | grep 200'] {'logoutput': True, 'tries': 5, 'try_sleep': 3}
200
2017-05-12 21:21:09,010 - Execute['curl -s -o /dev/null -w'%{http_code}' --negotiate -u: -k http://xxxx:8999/sessions | grep 200'] {'logoutput': True, 'tries': 3, 'user': 'livy', 'try_sleep': 1}
2017-05-12 21:21:09,149 - Retrying after 1 seconds. Reason: Execution of 'curl -s -o /dev/null -w'%{http_code}' --negotiate -u: -k http://xxx:8999/sessions | grep 200' returned 1. 
2017-05-12 21:21:10,286 - Retrying after 1 seconds. Reason: Execution of 'curl -s -o /dev/null -w'%{http_code}' --negotiate -u: -k http://xxxx:8999/sessions | grep 200' returned 1.

Command failed after 1 tries{code}





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)