[ 
https://issues.apache.org/jira/browse/HDDS-1631?focusedWorklogId=253106&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-253106
 ]

ASF GitHub Bot logged work on HDDS-1631:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Jun/19 13:30
            Start Date: 03/Jun/19 13:30
    Worklog Time Spent: 10m 
      Work Description: dineshchitlangia commented on issue #892: HDDS-1631. 
Fix auditparser smoketests
URL: https://github.com/apache/hadoop/pull/892#issuecomment-498257404
 
 
   @elek Thanks for filing this and providing the patch. The test failures do 
not look related to me. +1 non-binding.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 253106)
    Time Spent: 0.5h  (was: 20m)

> Fix auditparser smoketests
> --------------------------
>
>                 Key: HDDS-1631
>                 URL: https://issues.apache.org/jira/browse/HDDS-1631
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In HDDS-1518 we modified the location of the var and config files inside the 
> container.
> There are three problems with the current auditparser smokest:
>  1. The default audit log4j files are not part of the new config directory 
> (fixed with HDDS-1630)
>  2. The smoketest is executed in scm container instead of om
>  3. The log directory is hard coded
> The 2 and 3 will be fined in this patch. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to