You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by Madhavi Amirneni <ma...@us.ibm.com> on 2017/05/02 16:52:47 UTC
Review Request 58921: Ranger-1552: Ranger usersync or ranger kms not
able to
communicate to ranger admin and no exception or error seen in the ranger
user sync or kms logs.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58921/
-----------------------------------------------------------
Review request for ranger.
Repository: ranger
Description
-------
The default communication between Ranger admin and Ranger usersync or Ranger kms is SSL enabled. When there is an error during the hadoop keystore creation, there is no exception thrown but there was a non-zeor return code returned. However, ranger did not check/handle this error return code and continued, which has caused Ranger usersync to assume the communication to be normal and continue.
With this fix, when there is an error during the keystore creation, an error message is logged and the process will exit.
Diffs
-----
credentialbuilder/src/main/java/org/apache/ranger/credentialapi/buildks.java a7e433f
Diff: https://reviews.apache.org/r/58921/diff/1/
Testing
-------
Manual unit testing
Thanks,
Madhavi Amirneni
Re: Review Request 58921: Ranger-1552: Ranger usersync or ranger kms
not
able to communicate to ranger admin and no exception or error seen in the
ranger user sync or kms logs.
Posted by Madhavi Amirneni <ma...@us.ibm.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58921/
-----------------------------------------------------------
(Updated May 2, 2017, 5:03 p.m.)
Review request for ranger.
Repository: ranger
Description
-------
The default communication between Ranger admin and Ranger usersync or Ranger kms is SSL enabled. When there is an error during the hadoop keystore creation, there is no exception thrown but there was a non-zeor return code returned. However, ranger did not check/handle this error return code and continued, which has caused Ranger usersync to assume the communication to be normal and continue.
With this fix, when there is an error during the keystore creation, an error message is logged and the process will exit.
Diffs
-----
credentialbuilder/src/main/java/org/apache/ranger/credentialapi/buildks.java a7e433f
Diff: https://reviews.apache.org/r/58921/diff/1/
Testing (updated)
-------
Manual unit testing & Automated tests.
Thanks,
Madhavi Amirneni