[
https://issues.apache.org/jira/browse/AMBARI-25340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-25340:
------------------------------------------
Description:
Steps to reproduce
--------------------------
# Enable Hive LDAP authentication.
# Add below configs to hive-env
{noformat}
alert_ldap_username
alert_ldap_password{noformat}
# Now perform service check.
# It fails with below exception.
{noformat}
2019-07-16 10:28:42,298 - Execute['beeline -n hive -u
'jdbc:hive2://xxxxx:10000/;transportMode=binary' -n 'xxxx' -p '[PROTECTED]' -e
';' 2>&1 | awk '{print}' | grep -i -e 'Connected to:' -e 'Transaction
isolation:''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/',
'/usr/sbin/'], 'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'}
2019-07-16 10:28:45,880 - Connection to hdpnode02.aepsc.com on port 10000
failed
{noformat}
*Root cause:*
Ambari uses both the users in beeline. you can see hive as well as ldap user.
ideally it should only use LDAP user.
was:
Steps to reproduce
--------------------------
# Enable Hive LDAP authentication.
# Add below configs to hive-env
{noformat}
alert_ldap_username
alert_ldap_password{noformat}
# Now perform service check.
# It fails with below exception.
{noformat}
2019-07-16 10:28:42,298 - Execute['beeline -n hive -u
'jdbc:hive2://hdpnode02.aepsc.com:10000/;transportMode=binary' -n 'xxxx' -p
'[PROTECTED]' -e ';' 2>&1 | awk '{print}' | grep -i -e 'Connected to:' -e
'Transaction isolation:''] {'path': ['/bin/', '/usr/bin/',
'/usr/lib/hive/bin/', '/usr/sbin/'], 'timeout_kill_strategy': 2, 'timeout': 30,
'user': 'ambari-qa'}
2019-07-16 10:28:45,880 - Connection to hdpnode02.aepsc.com on port 10000
failed
{noformat}
*Root cause:*
Ambari uses both the users in beeline. you can see hive as well as ldap user.
ideally it should only use LDAP user.
> Hive service check fails when LDAP auth is enabled
> --------------------------------------------------
>
> Key: AMBARI-25340
> URL: https://issues.apache.org/jira/browse/AMBARI-25340
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.3
> Reporter: amarnath reddy pappu
> Assignee: amarnath reddy pappu
> Priority: Major
>
> Steps to reproduce
> --------------------------
> # Enable Hive LDAP authentication.
> # Add below configs to hive-env
> {noformat}
> alert_ldap_username
> alert_ldap_password{noformat}
> # Now perform service check.
> # It fails with below exception.
> {noformat}
> 2019-07-16 10:28:42,298 - Execute['beeline -n hive -u
> 'jdbc:hive2://xxxxx:10000/;transportMode=binary' -n 'xxxx' -p '[PROTECTED]'
> -e ';' 2>&1 | awk '{print}' | grep -i -e 'Connected to:' -e 'Transaction
> isolation:''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/',
> '/usr/sbin/'], 'timeout_kill_strategy': 2, 'timeout': 30, 'user':
> 'ambari-qa'}
> 2019-07-16 10:28:45,880 - Connection to hdpnode02.aepsc.com on port 10000
> failed
> {noformat}
> *Root cause:*
> Ambari uses both the users in beeline. you can see hive as well as ldap user.
> ideally it should only use LDAP user.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
