-
Notifications
You must be signed in to change notification settings - Fork 100
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
lmdb reindex is broken if index type is specified #6316
Comments
progier389
added a commit
that referenced
this issue
Sep 6, 2024
While reindexing using task or offline reindex, if the attribute name contains the index type (for example :eq,pres) Then the attribute is not reindexed. Problem occurs when lmdb is used, things are working fine with bdb. Solution: strip the index type in reindex as it is done in bdb case. Anyway the reindex design requires that for a given attribute all the configured index types must be rebuild. Issue: #6316 Reviewed by: @tbordaz, @droideck (Thanks!)
edewata
added a commit
to edewata/pki
that referenced
this issue
Sep 6, 2024
The tests for CA with secure DS connection (including cloning) have been updated to use DS containers instead of DS RPM packages from Fedora to avoid DS issue #6316. 389ds/389-ds-base#6316
edewata
added a commit
to dogtagpki/pki
that referenced
this issue
Sep 9, 2024
The tests for CA with secure DS connection (including cloning) have been updated to use DS containers instead of DS RPM packages from Fedora to avoid DS issue #6316. 389ds/389-ds-base#6316
edewata
added a commit
to edewata/pki
that referenced
this issue
Sep 9, 2024
The tests for CA with secure DS connection (including cloning) have been updated to use DS containers instead of DS RPM packages from Fedora to avoid DS issue #6316. 389ds/389-ds-base#6316
edewata
added a commit
to edewata/pki
that referenced
this issue
Sep 9, 2024
The tests for CA with secure DS connection (including cloning) have been updated to use DS containers instead of DS RPM packages from Fedora to avoid DS issue #6316. 389ds/389-ds-base#6316
vashirov
pushed a commit
that referenced
this issue
Sep 16, 2024
While reindexing using task or offline reindex, if the attribute name contains the index type (for example :eq,pres) Then the attribute is not reindexed. Problem occurs when lmdb is used, things are working fine with bdb. Solution: strip the index type in reindex as it is done in bdb case. Anyway the reindex design requires that for a given attribute all the configured index types must be rebuild. Issue: #6316 Reviewed by: @tbordaz, @droideck (Thanks!)
vashirov
pushed a commit
that referenced
this issue
Sep 16, 2024
While reindexing using task or offline reindex, if the attribute name contains the index type (for example :eq,pres) Then the attribute is not reindexed. Problem occurs when lmdb is used, things are working fine with bdb. Solution: strip the index type in reindex as it is done in bdb case. Anyway the reindex design requires that for a given attribute all the configured index types must be rebuild. Issue: #6316 Reviewed by: @tbordaz, @droideck (Thanks!)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
Some freeipa tests are now failing because a reindex is not properly done although a reindex task is performed.
The issue is related to the fact that the task contains subtype -
Looks like it was a regression in some of the vlv fixes
Anyway the index type should always be ignored in tasks because reindexing only some specific types has no sense (because reindex recreate the db instance from scratch anyway ...)
A clear and concise description of what the bug is.
Package Version and Platform:
Steps to Reproduce
Steps to reproduce the behavior:
Expected results
Should have equality keys =value for both the suffix and the demo_user entry
A clear and concise description of what you expected to happen.
Additional context
Solution is to ignore the type when handling reindex task
Triaged: https://issues.redhat.com/browse/IDMDS-4641
The text was updated successfully, but these errors were encountered: