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.

Sign up for GitHub

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

Jump to bottom

db reindex corrupts RUV tombstone nsuniqueid index #4910

Closed
mreynolds389 opened this issue Sep 8, 2021 · 1 comment
Closed

db reindex corrupts RUV tombstone nsuniqueid index #4910

mreynolds389 opened this issue Sep 8, 2021 · 1 comment
Assignees
@mreynolds389
Milestone
1.4.3

Comments

@mreynolds389
Copy link
Contributor

Issue Description

A regression was introduced some time ago where we incorrectly skip the RUV tombstone entry when it comes to reindexing. So after a reindex the nsuniqueid index does not contain the RUV entry, and any search using the DN in a "base" search will fail which in turn breaks replication.
@mreynolds389 mreynolds389 added the needs triage The issue will be triaged during scrum label Sep 8, 2021
@mreynolds389 mreynolds389 self-assigned this Sep 8, 2021
@mreynolds389 mreynolds389 mentioned this issue Sep 8, 2021
Merged
mreynolds389 added a commit to mreynolds389/389-ds-base that referenced this issue Sep 9, 2021
@mreynolds389
Issue 4910 - db reindex corrupts RUV tombstone nsuiqueid index
f959f13 
Bug Description:  During a reindex task we skip the RUV tombstone entry,
                  which corrupts the nsuniqueid index.

Fix Description:  Make sure we still index nsuniqueid index for
                  the RUV tombstone entry.

relates: 389ds#4910

Reviewed by: firstyear & progier389 (Thanks!!)
mreynolds389 added a commit that referenced this issue Sep 9, 2021
@mreynolds389
Issue 4910 - db reindex corrupts RUV tombstone nsuiqueid index
7f610ec 
Bug Description:  During a reindex task we skip the RUV tombstone entry,
                  which corrupts the nsuniqueid index.

Fix Description:  Make sure we still index nsuniqueid index for
                  the RUV tombstone entry.

relates: #4910

Reviewed by: firstyear & progier389 (Thanks!!)
mreynolds389 added a commit that referenced this issue Sep 9, 2021
@mreynolds389
Issue 4910 - db reindex corrupts RUV tombstone nsuiqueid index
97f8433 
Bug Description:  During a reindex task we skip the RUV tombstone entry,
                  which corrupts the nsuniqueid index.

Fix Description:  Make sure we still index nsuniqueid index for
                  the RUV tombstone entry.

relates: #4910

Reviewed by: firstyear & progier389 (Thanks!!)
mreynolds389 added a commit that referenced this issue Sep 9, 2021
@mreynolds389
Issue 4910 - db reindex corrupts RUV tombstone nsuiqueid index
c47460e 
Bug Description:  During a reindex task we skip the RUV tombstone entry,
                  which corrupts the nsuniqueid index.

Fix Description:  Make sure we still index nsuniqueid index for
                  the RUV tombstone entry.

relates: #4910

Reviewed by: firstyear & progier389 (Thanks!!)
@mreynolds389 mreynolds389 removed the needs triage The issue will be triaged during scrum label Sep 9, 2021
@mreynolds389 mreynolds389 added this to the 1.4.3 milestone Sep 9, 2021
@mreynolds389
Copy link
Contributor Author

mreynolds389 commented Sep 9, 2021 •
edited
Loading

3f7a2fa..154957c 389-ds-base-2.0 -> 389-ds-base-2.0
03a6752..97f8433 389-ds-base-1.4.4 -> 389-ds-base-1.4.4
5321911..c47460e 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

mreynolds389 added a commit that referenced this issue Sep 9, 2021
@mreynolds389
Issue 4910 - db reindex corrupts RUV tombstone nsuiqueid index
154957c 
Bug Description:  During a reindex task we skip the RUV tombstone entry,
                  which corrupts the nsuniqueid index.

Fix Description:  Make sure we still index nsuniqueid index for
                  the RUV tombstone entry.

relates: #4910

Reviewed by: firstyear & progier389 (Thanks!!)
@progier389 progier389 mentioned this issue Sep 22, 2021
Open
@mreynolds389 mreynolds389 mentioned this issue Oct 28, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mreynolds389 mreynolds389

Labels
None yet
Projects
None yet
Milestone
1.4.3
Development

No branches or pull requests
1 participant
@mreynolds389