[ https://issues.apache.org/jira/browse/AMBARI-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218756#comment-15218756 ]
Hadoop QA commented on AMBARI-15241: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12796122/AMBARI-15241.v2.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6102//console This message is automatically generated. > Basic Operational Audit Logging > ------------------------------- > > Key: AMBARI-15241 > URL: https://issues.apache.org/jira/browse/AMBARI-15241 > Project: Ambari > Issue Type: New Feature > Components: ambari-server > Reporter: Sebastian Toader > Assignee: Daniel Gergely > Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15241.v2.patch > > > Ambari should audit operational events (including user, timestamp, etc) such > as: start, stop, restart, move, add/delete service, add/delete component, > enable/disable kerberos, enter/leave maintenance mode, > create/edit/enable/disable alerts. This should also include user/group role > changes (including Ambari Admin flag). > This information should be available in an operational log. > When an operation is executed in Ambari, append an entry to a history log > showing: > The timestamp is when the operation is started > The user is the logged in user > The operation is what is currently displayed in the operations UI > The success/fail is what is displayed in the UI when the operation is > completed > Comment is an optional field the user can supply -- This message was sent by Atlassian JIRA (v6.3.4#6332)