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

ASF GitHub Bot commented on AMBARI-19283:
-----------------------------------------

GitHub user dsantesteban opened a pull request:

    https://github.com/apache/ambari/pull/45

    Resolution for AMBARI-19283

    These changes will allow Ambari stack extensions to use alert scripts.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dsantesteban/ambari trunk

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ambari/pull/45.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #45
    
----
commit 35d210de808e5884bd5bf12b0de0aa1a654cd4a3
Author: Diego Santesteban <[email protected]>
Date:   2016-12-22T18:01:30Z

    Changes to resolve AMBARI-19283

commit a1d093b03d0ef5de9ded9902cd89a0254917acfc
Author: Diego Santesteban <[email protected]>
Date:   2016-12-22T18:04:59Z

    One more change (keeping function params within column 80)

----


> Ambari agent doesn't find alert scripts in a stack extension
> ------------------------------------------------------------
>
>                 Key: AMBARI-19283
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19283
>             Project: Ambari
>          Issue Type: Bug
>          Components: alerts
>    Affects Versions: 2.4.2
>            Reporter: Diego Santesteban
>             Fix For: 2.5.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> When a service in a stack extension includes alerts, Ambari cannot find the 
> scripts for the alerts. It's only looking in the cache/stacks and 
> cache/host_scripts directories. Ambari needs to check the cache/extensions 
> directory as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to