You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Myroslav Papirkovskyi (JIRA)" <ji...@apache.org> on 2018/02/01 17:56:00 UTC
[jira] [Resolved] (AMBARI-22870) Ranger fails to install
(branch-3.0-perf)
[ https://issues.apache.org/jira/browse/AMBARI-22870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myroslav Papirkovskyi resolved AMBARI-22870.
--------------------------------------------
Resolution: Fixed
Merged into branch-3.0-perf
> Ranger fails to install (branch-3.0-perf)
> -----------------------------------------
>
> Key: AMBARI-22870
> URL: https://issues.apache.org/jira/browse/AMBARI-22870
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 3.0.0
> Reporter: Myroslav Papirkovskyi
> Assignee: Myroslav Papirkovskyi
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> jdbc related properties like:
> {noformat}
> previous_custom_mysql_jdbc_name, custom_mysql_jdbc_name, custom_postgres_jdbc_name, previous_custom_postgres_jdbc_name
> {noformat}
> also
> {noformat}
> gpl_license_accepted
> {noformat}
> are missing.
> We should sent them in metadata/ambariLevelParams in order for Ranger andother db dependent services to work properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)