[
https://issues.apache.org/jira/browse/AMBARI-9075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271968#comment-14271968
]
Hudson commented on AMBARI-9075:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit-docker #717 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/717/])
AMBARI-9075. Alerts after move Oozie Server (sgunturi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=25a3a1962c1f843e07ed2fd7eeb337b9f5e67580)
* ambari-web/app/controllers/main/service/reassign/step4_controller.js
> Alerts after move Oozie Server
> ------------------------------
>
> Key: AMBARI-9075
> URL: https://issues.apache.org/jira/browse/AMBARI-9075
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 2.0.0
>
> Attachments: AMBARI-9075.patch, Screen Shot 2015-01-09 at 10.52.34
> AM.png
>
>
> ● Fresh install of the ambariserver.
> ● Create a new cluster with specific services. Oozie with new derby database
> ● Move the Oozie Server to another host machine. :
> # Select Move Oozie Server from the Service Actions drop down box
> # select the host to assign the new master to
> # click next.
> # click Deploy.
> # execute the manual steps as instructed on the wizard
> # click next
> # click Complete to exit the wizard.
> *Expected*
> no alerts
> *Actual*
> 2 alerts
> Oozie Server Web UI
> * Connection failed to http://c6401.ambari.apache.org:11000
> Oozie Server Status
> * Error: IO_ERROR : java.net.MalformedURLException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
