ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9947) Oozie alert after ambari upgrade 1.7.0->2.0.0 secured cluster
Date Thu, 05 Mar 2015 19:19:43 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-9947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349315#comment-14349315
] 

Hudson commented on AMBARI-9947:
--------------------------------

ABORTED: Integrated in Ambari-branch-2.0.0 #12 (See [https://builds.apache.org/job/Ambari-branch-2.0.0/12/])
AMBARI-9947 Oozie alert after ambari upgrade 1.7.0->2.0.0 secured cluster (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e9623812ea36a4e3b7df95358e34636852a412f3)
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py


> Oozie alert after ambari upgrade 1.7.0->2.0.0 secured cluster
> -------------------------------------------------------------
>
>                 Key: AMBARI-9947
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9947
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9947.patch
>
>
> After upgrading secured cluster and restarting all services oozie has warning alert:
> Oozie Server Web UI
> HTTP 500 response in 0.000 seconds
> STR:
> 1. Installed ambari 1.7.0 on 3-node cluster, all services
> 2. Enabl security
> 3. Upgrade ambari to 2.0.0
> 4. Stop all services
> 5. Start all services



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message