[
https://issues.apache.org/jira/browse/AMBARI-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011271#comment-15011271
]
Hudson commented on AMBARI-13940:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #3860 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3860/])
AMBARI-13940 Moving oozie fails at DB connection. (atkach) (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=31c99869f341dec5c9b7821dcd5c5a9247f27ada])
* ambari-web/app/views/common/controls_view.js
* ambari-web/test/views/common/controls_view_test.js
* ambari-web/test/controllers/main/service/reassign/step4_controller_test.js
* ambari-web/app/controllers/main/service/reassign/step4_controller.js
> Moving oozie fails at DB connection
> -----------------------------------
>
> Key: AMBARI-13940
> URL: https://issues.apache.org/jira/browse/AMBARI-13940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13940.patch,
> DB_Connection_err_Move_Oozie_server.png
>
>
> Moving oozie is failing at "Confirm configuration" step at DB connection.
> Attached is the screenshot of error.
> NOTE: nothing in tests have changed. We are using same steps to install
> mysql-connector, ambari-server setup for mysql and user properties for
> "Existing mysql connection"
> which are "ooziedb", "oozieuser", "password" as seen on ooze config page.
> Please take a look at why move ooze server failing at db connection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
