[
https://issues.apache.org/jira/browse/AMBARI-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584204#comment-14584204
]
Hadoop QA commented on AMBARI-11894:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12739319/AMBARI-11894.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3164//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3164//console
This message is automatically generated.
> Blueprint export incorrectly removes Oozie heapsize settings from exported
> Blueprint
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-11894
> URL: https://issues.apache.org/jira/browse/AMBARI-11894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11894.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The Blueprint processor incorrectly removes some Oozie heapsize settings that
> are defined in the "oozie-env" configuration type.
> Steps to reproduce:
> 1. Deploy a single-node cluster with Ambari UI with HDFS, Yarn, and Oozie.
> 2. Use the REST API to export a Blueprint from this running cluster;
> http://host:port/api/v1/clusters/clusterone?format=blueprint
> The following properties, normally included in "oozie-env", are not present
> in the exported Blueprint:
> "oozie_heapsize"
> "oozie_permsize"
> I'm working on a fix for this issue, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
