[
https://issues.apache.org/jira/browse/AMBARI-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251147#comment-15251147
]
Hadoop QA commented on AMBARI-16001:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799835/rb45592.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.HostResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6569//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6569//console
This message is automatically generated.
> Fix bad entry in hbase-env.sh that were added as part of 2.2.0-2.2.1.1 upgrade
> ------------------------------------------------------------------------------
>
> Key: AMBARI-16001
> URL: https://issues.apache.org/jira/browse/AMBARI-16001
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.2
> Reporter: Ajit Kumar
> Assignee: Ajit Kumar
> Fix For: 2.2.2
>
> Attachments: rb45592.patch
>
>
> Ambari upgrades, 2.2.0-2.2.1.1 adds a bad entry to the hbase-env
> {code}export HBASE_OPTS="-Djava.io.tmpdir={{java_io_tmpdir}}"{code}
> With broken hbase-env user cannot run any mapreduce services for hbase.
> Currently it needs to be fixed manually.
> {code}
> export HBASE_OPTS="${HBASE_OPTS} -Djava.io.tmpdir={{java_io_tmpdir}}"
> {code}
> It will be good if just upgrading to 2.2.2 fixes this issue rather than
> mucking around with configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)