str2entry_dupcheck not all errors are logged

389ds / 389-ds-base

The enterprise-class Open Source LDAP server for Linux

https://www.port389.org/

Other

210 stars 88 forks source link

str2entry_dupcheck not all errors are logged #2182

Open 389-ds-bot opened 4 years ago

389-ds-bot commented 4 years ago

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49123

Created at 2017-02-04 05:00:28 by firstyear (@Firstyear)
Assigned to nobody

A number of error cases in str2entry_dupcheck are only logged at LOG_TRACE, when they should be logged at an error level (WARNING, ERR). This can cause silent failures of imports.

389-ds-bot commented 4 years ago

Comment from firstyear (@Firstyear) at 2017-02-11 23:08:57

Metadata Update from @Firstyear:

Issue set to the milestone: 0.0 NEEDS_TRIAGE

389-ds-bot commented 4 years ago

Comment from mreynolds (@mreynolds389) at 2017-03-02 22:26:30

Metadata Update from @mreynolds389:

Issue close_status updated to: None
Issue set to the milestone: 1.3.7 backlog (was: 0.0 NEEDS_TRIAGE)

389-ds-bot commented 4 years ago

Comment from mreynolds (@mreynolds389) at 2019-08-23 20:49:38

Metadata Update from @mreynolds389:

Custom field reviewstatus adjusted to None
Issue set to the milestone: FUTURE (was: 1.3.7 backlog)

389-ds-bot commented 4 years ago

Comment from mreynolds (@mreynolds389) at 2020-04-29 16:54:32

Metadata Update from @mreynolds389:

Issue set to the milestone: 1.4.4 (was: FUTURE)
Issue tagged with: Easyfix