[
https://issues.apache.org/jira/browse/AMBARI-12130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599996#comment-14599996
]
Hudson commented on AMBARI-12130:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2992 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2992/])
AMBARI-12130. Ambari Upgrade: oozie alert broken URL (Eugene Chekanskiy via
smohanty) (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ecb7eb740bc1cdaa976e9a1ea38fd34254f54b36)
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java
> Ambari Upgrade: oozie alert broken URL
> --------------------------------------
>
> Key: AMBARI-12130
> URL: https://issues.apache.org/jira/browse/AMBARI-12130
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12130.patch, oozie-alert.tiff
>
>
> 1) Upgraded from Ambari 201 + HDP 2.2 -> Ambari 2.1.0 (ambari only upgrade)
> 2) Oozie alert shows warning. Looks like the URL it's checking is now wrong.
> has an extra /oozie.
> FWIW, The oozie.base.url config is
> "http://c6402.ambari.apache.org:11000/oozie";
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
