[
https://issues.apache.org/jira/browse/AMBARI-18039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-18039:
----------------------------------
Description: 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 (was: 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 used query/filter in the logs)
> 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)
