ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17967) Provide an option not to log ambari-agent command output for user custom script action
Date Sat, 30 Jul 2016 14:14:20 GMT

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

Sumit Mohanty commented on AMBARI-17967:
----------------------------------------

Manual UT run results:
{code}
Tests in error:
  DataStoreImplTest.initializationError ยป NoClassDefFound org/apache/ambari/serv...

Tests run: 4564, Failures: 0, Errors: 1, Skipped: 34

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views ...................................... SUCCESS [5.162s]
[INFO] Ambari Metrics Common ............................. SUCCESS [13.880s]
[INFO] Ambari Server ..................................... FAILURE [2:11:45.637s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:12:05.429s
[INFO] Finished at: Fri Jul 29 22:57:36 PDT 2016
[INFO] Final Memory: 50M/577M
[INFO] ------------------------------------------------------------------------
{code}

UT failure unrelated to the patch.

> Provide an option not to log ambari-agent command output for user custom script action
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17967
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17967
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17967.patch
>
>
> Custom actions is a way to create a set of commands that can perform specific actions
on the cluster. Class of actions typically involve initialization, setup, and cleanup - different
than the start/stop/configure/install etc.
> By default all command output gets logged. It should be possible for the custom actions
to indicate if the output should be logged as custom action output may contain PII information.



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

Mime
View raw message