-
Notifications
You must be signed in to change notification settings - Fork 104
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
The import has been aborted because the entry does not have a parent entry #438
Comments
please check "exists parent entry for 'n=0,ou=Registrations,o=rA' in ~/dev/tmp/content.ldif |
This is the same LDIF I was using in my original ticket @vharseko. But, nonetheless, the following is the very top of the file:
Procedure:
Load output:
Yet, it most certainly DOES have a parent (see the top of this reply). But, to prove the point even more:
The parent did, in fact, make it to the DB ... Again,
... and confirm again by
|
try option --threadCount 1 from import-ldif
|
Unfortunately, no joy. See the diagnostics below, and see some WEIRD results at the very end.
Log output (note: 14th log event confirms thread count == 1)
Start server and do
So, in case you didn't see above, it says zero (0) entries in rA, so naturally my
WOW: 0 < 62620 In looking at the entries, I notice they're ALL No For your reference, I'm going to identify the
|
please attach test ldif for reproduce |
I can only give you an excerpt, because many email addresses are in the file. Even if they're already publicized, I'd rather not post them here. 🤐 FORTUNATELY, even the small excerpt triggers the issue. See attached (note I had to rename it to include ".txt" as ".ldif" is not allowed). I even threw a I also attached the schema file again, just in case. And, just to show you the excerpt triggers the same issue on a freshly deleted/created backend:
|
online import works done ? |
Online method does not seem to work:
Online import:
As you can see, in addition to the "no parent" issue, it is also complaining about degraded indices, which it shouldn't because the backend was just initialized. I don't see that behavior in |
try with -S
|
Exact same result as without
Seems it makes no difference. Also, I don't think schema validation would account for these index errors. |
… aborted because the entry does not have a parent entry"
@JesseCoretta please check artifact from https://github.com/OpenIdentityPlatform/OpenDJ/actions/runs/11466356948 |
@vharseko -- thank you. Will check once the builds are released, looks like its almost finished. EDIT: build failed, though I see they're mostly MacOS (#445). Not seeing the release artifacts as a result. I'll check back in a few hours to see if the issue was resolved. On a related note -- would this explain the build issues I experienced over the weekend? I tried to prepare #439 but unit tests were succeeding on my local system, and failing in our docker system. |
… aborted because the entry does not have a parent entry"
OpenDJ/.github/workflows/build.yml Lines 49 to 58 in 5cd2c6e
use -Pprecommit switch
|
fixed https://github.com/OpenIdentityPlatform/OpenDJ/actions/runs/11501698117 |
@vharseko -- I cannot confirm. With that link, I only see a single downloadable build and it is MacOS. |
MacOS-8 is cross platform |
Using the MacOS build produces some unusual results.
Line of interest:
So it does not seem to be fixed. FWIW ... this is the same data you've seen previously. |
@vharseko -- ah, on a hunch, I tried your
But what is curious is that the structure of this LDIF works in OpenLDAP, 389DS, et al ... so I am uncertain why |
I will check this case additionally |
use --skipSchemaValidation or switch to online import |
Fine |
… entry does not have a parent entry" (#444)
Describe the bug
Re-emergence of #431
On a fresh backend, I am once again seeing
Commands run:
Note, I also tried without
--clearBackend
with the same result.The text was updated successfully, but these errors were encountered: