EntryUUID fixup to correct invalid entryuuids #4877
Assignees
Labels
needs triage
The issue will be triaged during scrum
Comments
Firstyear
added a commit
to Firstyear/389-ds-base
that referenced
this issue
Aug 19, 2021
Bug Description: Due to changing the syntax of EntryUUID's to string, we may have invalid EntryUUID's imported into the database. Fix Description: To resolve this during a fixup we validate that Uuid's have a valid syntax. If they do not, we regenerate them. fixes: 389ds#4877 Author: William Brown <william@blackhats.net.au> Review by: ???
Firstyear
added a commit
that referenced
this issue
Aug 19, 2021
Bug Description: Due to changing the syntax of EntryUUID's to string, we may have invalid EntryUUID's imported into the database. Fix Description: To resolve this during a fixup we validate that Uuid's have a valid syntax. If they do not, we regenerate them. fixes: #4877 Author: William Brown <william@blackhats.net.au> Review by: @mreynolds389
Firstyear
added a commit
that referenced
this issue
Aug 23, 2021
Bug Description: Due to changing the syntax of EntryUUID's to string, we may have invalid EntryUUID's imported into the database. Fix Description: To resolve this during a fixup we validate that Uuid's have a valid syntax. If they do not, we regenerate them. fixes: #4877 Author: William Brown <william@blackhats.net.au> Review by: @mreynolds389
Firstyear
added a commit
that referenced
this issue
Aug 23, 2021
Bug Description: Due to changing the syntax of EntryUUID's to string, we may have invalid EntryUUID's imported into the database. Fix Description: To resolve this during a fixup we validate that Uuid's have a valid syntax. If they do not, we regenerate them. fixes: #4877 Author: William Brown <william@blackhats.net.au> Review by: @mreynolds389
Firstyear
added a commit
that referenced
this issue
Aug 23, 2021
Bug Description: Due to changing the syntax of EntryUUID's to string, we may have invalid EntryUUID's imported into the database. Fix Description: To resolve this during a fixup we validate that Uuid's have a valid syntax. If they do not, we regenerate them. fixes: #4877 Author: William Brown <william@blackhats.net.au> Review by: @mreynolds389
tbordaz
pushed a commit
that referenced
this issue
Jun 10, 2022
Bug Description: Due to changing the syntax of EntryUUID's to string, we may have invalid EntryUUID's imported into the database. Fix Description: To resolve this during a fixup we validate that Uuid's have a valid syntax. If they do not, we regenerate them. fixes: #4877 Author: William Brown <william@blackhats.net.au> Review by: @mreynolds389
droideck
added a commit
that referenced
this issue
Oct 11, 2022
Description: Bring back the entryuuid validation in the fixup task. The part of the code was removed during the cherry-picking to the older branch (389-ds-base-2.0), and its tests start to fail. Related: #4878 Related: #4877 Related: #4776 Related: #4775 Reviewed by: @Firstyear (Thanks!)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Relates #4872 - after the change of this to str syntax, we need a way to fix invalid entryuuids if they are imported.
The text was updated successfully, but these errors were encountered: