[jira] [Commented] (AMBARI-14033) Wrong Audit JDBC URL generated, even though JDBC URL format is overridden by user

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-14033:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12774049/AMBARI-14033.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4380//console

This message is automatically generated.

> Wrong Audit JDBC URL generated, even though JDBC URL format is overridden by user
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-14033
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14033
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.3
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.2.0, 2.1.3
>
>         Attachments: AMBARI-14033.patch
>
>
> *Steps to reproduce:*
> -- Install Ranger with Oracle 12C
> -- Use SID format for DB host (host:port:SID) e.g. hostname:1521:ORCL
> -- Override connect string (jdbc:oracle:thin:@hostname:1521:ORCL - note that there is no //, which was generated by Ambari, but should be removed to get it to work)
> -- Complete the install
> -- Ranger will work fine, but DB auditing will not work
> *Root Cause*
> When JDBC string is overridden, ranger-admin-site.xml->ranger.jpa.jdbc.url is properly generated.
> But,  {{ranger-admin-site.xml->ranger.jpa.audit.jdbc.url}} and {{ranger-<component>\-audit.xml\->xasecure.audit.destination.db.jdbc.url}} are generated wrong. They both refer to {{audit_jdbc_url}} macro, which is apparently calculated incorrectly.
> *Workaround*
> Manually override  ranger.jpa.audit.jdbc.url and xasecure.audit.destination.db.jdbc.url
> *Actual solution*
> Calculate the variable properly, so that user does not have to enter it again.



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