[ 
https://issues.apache.org/jira/browse/AMBARI-13189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906163#comment-14906163
 ] 

Hari Sekhon commented on AMBARI-13189:
--------------------------------------

I just reproduced this again thinking maybe it was just the issue of leaving 
Ranger as the Hive authorizer but the other configs undefined as seen in the 
screenshot the config revision diff was not changing the authorizer settings as 
the Settings tabs at the top left was greyed out (I think this is what 
AMBARI-13000 was documenting as I'm still on Ambari 2.1.0).

So I then changed the authorizer by hand to SQLStdAuth and the exact same error 
occurred as shown in the original post above when trying to restart the Hive 
service. I'm not sure why it would need any of those Ranger settings when the 
Ranger authorization is not the selected one, this must surely be a bug?

> Ranger Config Revert incomplete - breaks Hive service restart on HCat client 
> with error "resource_management.core.exceptions.Fail: Configuration parameter 
> 'REPOSITORY_CONFIG_PASSWORD' was not found in configurations dictionary!"
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13189
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13189
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>         Environment: HDP 2.3 + Kerberos + Ranger
>            Reporter: Hari Sekhon
>            Priority: Blocker
>         Attachments: Screen Shot 2015-09-24 at 10.55.57.png, Screen Shot 
> 2015-09-24 at 11.01.56.png, Screen Shot 2015-09-24 at 11.02.14.png, Screen 
> Shot 2015-09-24 at 11.02.23.png, Screen Shot 2015-09-24 at 11.02.34.png, 
> Screen Shot 2015-09-24 at 11.02.45.png, Screen Shot 2015-09-24 at 
> 11.03.03.png, Screen Shot 2015-09-24 at 11.03.14.png
>
>
> Due to the Ambari restart bug upon Ranger integration (AMBARI-13168), 
> reverting the Ranger configuration change in Hive using the in-built Ambari 
> revision control fails to undo all the Ranger related changes and the service 
> instead fails to restart on the very first HCat client with the following 
> error instead:
> {code}Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hcat_client.py",
>  line 56, in <module>
>     HCatClient().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
>     method(env)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 444, in restart
>     self.install(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hcat_client.py",
>  line 31, in install
>     import params
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params.py",
>  line 26, in <module>
>     from params_linux import *
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py",
>  line 483, in <module>
>     repo_config_password = 
> unicode(config['configurations']['ranger-hive-plugin-properties']['REPOSITORY_CONFIG_PASSWORD'])
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 81, in __getattr__
>     raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'REPOSITORY_CONFIG_PASSWORD' was not found in configurations dictionary!{code}
> This appears to be different to AMBARI-13000 as the 
> hive.security.authorization.manager was reverted to 
> org.apache.hadoop.hive.ql.security.authorization.plugin.sqlstd.SQLStdConfOnlyAuthorizerFactory



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to