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

Hudson commented on AMBARI-21182:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7591 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7591/])
AMBARI-21182. Agent Host Disk Usage Alert Hardcodes the Stack Directory 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d21d434a16ec3078f9c2098327b559476bab8bb1])
* (edit) ambari-server/src/test/python/host_scripts/TestAlertDiskSpace.py


> Agent Host Disk Usage Alert Hardcodes the Stack Directory
> ---------------------------------------------------------
>
>                 Key: AMBARI-21182
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21182
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21182.patch
>
>
> The Host Disk Usage alert currently hard codes the stack location directly
> into the script:
>     
>     
>     
>     # the location where HDP installs components when using HDP 2.2+
>     STACK_HOME_DIR = "/usr/hdp"
>     # the location where HDP installs components when using HDP 2.0 to 2.1
>     STACK_HOME_LEGACY_DIR = "/usr/lib"
>     # determine the location of HDP home
>       stack_home = None
>       if os.path.isdir(STACK_HOME_DIR):
>         stack_home = STACK_HOME_DIR
>       elif os.path.isdir(STACK_HOME_LEGACY_DIR):
>         stack_home = STACK_HOME_LEGACY_DIR
>     
> On clusters where a different stack is installed (such as `/usr/hdf`, the
> above logic incorrectly checks the `STACK_HOME_LEGACY_DIR`.
>   * The 2.0 and 2.1 code paths should be removed since they are not supported 
> anymore.
>   * We should parameterize STACK_HOME_DIR (or even better, use the stack 
> features JSON structure) to determine the home location to check.



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

Reply via email to