[
https://issues.apache.org/jira/browse/AMBARI-14080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028158#comment-15028158
]
Hudson commented on AMBARI-14080:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3914 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3914/])
AMBARI-14080. Test connection for Ranger from ambari takes the DB flavor
(jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3c1944c187ee429a0a87ac1ddd135d7109d724c2])
* ambari-web/app/views/common/configs/widgets/test_db_connection_widget_view.js
> Test connection for Ranger from ambari takes the DB flavor selected before
> --------------------------------------------------------------------------
>
> Key: AMBARI-14080
> URL: https://issues.apache.org/jira/browse/AMBARI-14080
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14080.patch
>
>
> *STR:*
> # On Add Service wizard while adding Ranger service, select MySQL database
> # Test connection for system DBA user.This happens successfully
> # Switch the DB to MSSQL
> # Again try test connection
> *Expected Result:* MSSQL Jar should be used for test connection and if MSSQL
> is correctly setup test connection should pass
> *Actual Result:* MySQL connection Jar is used and test connection fails
> This is due to the incorrect API invoked by the ambari-web.
> dbname field in the API is not updated when database flavor is changed and
> API is triggered via "Test Connection" action
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
