[
https://issues.apache.org/jira/browse/AMBARI-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588302#comment-14588302
]
Hudson commented on AMBARI-11902:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2936 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2936/])
AMBARI-11902. Oozie Server Status alert fails in a SSL enabled Oozie
environment (dlysnichenko) (dlysnichenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=adbfdb8050fc5ca9f96f921a278f99cdb0d56424)
*
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/alerts/alert_check_oozie_server.py
> Oozie Server Status alert fails in a SSL enabled Oozie environment
> ------------------------------------------------------------------
>
> Key: AMBARI-11902
> URL: https://issues.apache.org/jira/browse/AMBARI-11902
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Eugene Chekanskiy
> Assignee: Eugene Chekanskiy
> Fix For: 2.1.0
>
>
> When enabling Oozie server SSL, the oozie.base.url is an HTTP URL, but
> redirects users to the HTTPS:// resource using a 302. Alert fails because it
> is not expecting a 302.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
