You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2015/11/18 12:42:11 UTC
[jira] [Commented] (AMBARI-13940) Moving oozie fails at DB
connection
[ https://issues.apache.org/jira/browse/AMBARI-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010824#comment-15010824 ]
Andrii Tkach commented on AMBARI-13940:
---------------------------------------
10185 tests complete (13 seconds)
104 tests pending
> 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)