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-11058) Check oozie.https properties to generate oozie war -secure
Date Tue, 12 May 2015 17:16:02 GMT

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

Hudson commented on AMBARI-11058:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #2571 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2571/])
AMBARI-11058 - Check oozie.https properties to generate oozie war -secure (tbeerbower) (tbeerbower:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bb9963c7833b5441c83bbae544edea028377a2fd)
* ambari-server/src/test/python/stacks/2.0.6/configs/secured.json
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py


> Check oozie.https properties to generate oozie war -secure
> ----------------------------------------------------------
>
>                 Key: AMBARI-11058
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11058
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 1.2.1
>
>         Attachments: AMBARI-11058.patch
>
>
> We should trigger a -secure prepare-war step if we notice any oozie.https.* properties
added in the Custom oozie-site.
> {code}
> oozie.https.port=11443
> oozie.https.keystore.file=/home/oozie/.keystore
> oozie.https.keystore.pass=password
> {code}



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

Mime
View raw message