[
https://issues.apache.org/jira/browse/AMBARI-12524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640477#comment-14640477
]
Hadoop QA commented on AMBARI-12524:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747015/AMBARI-12524.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/3461//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3461//console
This message is automatically generated.
> RU: prerequisites have a couple issues
> --------------------------------------
>
> Key: AMBARI-12524
> URL: https://issues.apache.org/jira/browse/AMBARI-12524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.1
>
> Attachments: AMBARI-12524.patch
>
>
> Installed HDP 2.2 cluster, then installed HDP 2.3. clicked perform upgrade.
> The prerequisite checks had a couple issues:
> 1) The Hive Metastore warning is missing "Failed on:" text. Should that have
> said "HIVE"?
> 2) The config changes, show changing the yarn.admin.acl. I used custom
> service account name "jyarn" so it looks like it will preserve my setting in
> the Resulting Value (which is correct and good). But including this diff
> seemed strange.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)