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

Hadoop QA commented on AMBARI-20664:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12861715/AMBARI-20664.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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/11280//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11280//console

This message is automatically generated.

> Remove hardcoding of /usr/hdp by AMBARI-20543 needed for IBM Power
> ------------------------------------------------------------------
>
>                 Key: AMBARI-20664
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20664
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20664.patch
>
>
> <https://issues.apache.org/jira/browse/AMBARI-20543> hardcoded /usr/hdp inside
> common-services for several services. It should instead use `stack_root`,
> which was one of the comments during the code review.
> An Ambari Upgrade from 2.5.0 to 2.5.1 should fix those properties via the
> Upgrade Catalog.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to