[
https://issues.apache.org/jira/browse/AMBARI-18039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409274#comment-15409274
]
Olivér Szabó commented on AMBARI-18039:
---------------------------------------
committed to trunk:
{code:java}
commit 4b76d2eb756028746d1911c32d87bd4179bd484f
Author: oleewere <[email protected]>
Date: Fri Aug 5 11:37:36 2016 +0200
AMBARI-18039. Ldap Sync filter logged out after the ldapsearch query
happens (oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 70b20b20bd21d223838d4426e87b88abfe302878
Author: oleewere <[email protected]>
Date: Fri Aug 5 11:37:36 2016 +0200
AMBARI-18039. Ldap Sync filter logged out after the ldapsearch query
happens (oleewere)
{code}
> Ldap sync filter logged out after the ldapsearch query happens
> --------------------------------------------------------------
>
> Key: AMBARI-18039
> URL: https://issues.apache.org/jira/browse/AMBARI-18039
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.4.0
>
> Attachments: AMBARI-18039.patch
>
>
> With TRACE log level, one of the filter logged out after the ldapsearch query
> happens, that can cause if the ldapsearch query fails, then we cannot see the
> query/filter in the logs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
