Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

str2entry_dupcheck not all errors are logged #2182 #6023

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

kimettog
Copy link
Contributor

@kimettog kimettog commented Jan 2, 2024

Issue ##### -

Bug Description:

str2entry_dupcheck not all errors are logged #2182

Fix Description:

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.

relates: #2182

Author: Gilbert Kimetto

Reviewed by: Simon Pichugi

@kimettog kimettog requested a review from droideck January 2, 2024 17:19
@kimettog kimettog self-assigned this Jan 2, 2024
ldap/servers/slapd/entry.c Outdated Show resolved Hide resolved
ldap/servers/slapd/entry.c Show resolved Hide resolved
@kimettog kimettog force-pushed the gk_str2_entrydupcheck branch 3 times, most recently from d991c65 to e978a41 Compare January 11, 2024 19:05
Copy link
Member

@droideck droideck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I've tried to import perfectly fine LDIF, and it gave me a lot of false warnings...
Steps to reproduce:

  1. Install an instance with sample entries
  2. Export a suffix from UI (Database - Suffixes - Suffix Tasks - Export Suffix) - Name the ldif.
  3. Import the suffix from UI (Database - Suffixes - Suffix Tasks - Initialise Suffix) - Choose the ldif.
  4. Check the logs for WARNs.

Could you please add another test that will check for clean export-import?
And we need to ensure that the logs are not filled with false warnings.

@kimettog kimettog force-pushed the gk_str2_entrydupcheck branch from e978a41 to 75c9cc9 Compare January 31, 2024 17:02
@kimettog kimettog force-pushed the gk_str2_entrydupcheck branch 3 times, most recently from f9bc320 to 1589797 Compare February 8, 2024 18:54
@kimettog kimettog marked this pull request as draft February 8, 2024 18:55
@kimettog kimettog force-pushed the gk_str2_entrydupcheck branch 6 times, most recently from 2f6ed7f to 1f10a70 Compare February 15, 2024 18:24
@kimettog kimettog marked this pull request as ready for review February 15, 2024 19:50
@kimettog kimettog force-pushed the gk_str2_entrydupcheck branch 3 times, most recently from e7a2fc3 to 565df36 Compare February 18, 2024 23:40
@kimettog kimettog force-pushed the gk_str2_entrydupcheck branch from 565df36 to 7a8af03 Compare May 2, 2024 17:12
@kimettog kimettog force-pushed the gk_str2_entrydupcheck branch 3 times, most recently from ad8773e to 59e78e9 Compare June 20, 2024 15:35
@kimettog kimettog force-pushed the gk_str2_entrydupcheck branch from 59e78e9 to fdeed50 Compare June 27, 2024 15:58
@kimettog kimettog marked this pull request as draft June 27, 2024 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants