You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/06/16 18:11:02 UTC
[jira] [Commented] (AMBARI-11902) Oozie Server Status alert fails
in a SSL enabled Oozie environment
[ https://issues.apache.org/jira/browse/AMBARI-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588287#comment-14588287 ]
Hudson commented on AMBARI-11902:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.1 #53 (See [https://builds.apache.org/job/Ambari-branch-2.1/53/])
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=98c54452da7e15f74face37c49d10995c7e99fdc)
* 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)