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

Export produces a non-importable ldif file #3291

Closed
389-ds-bot opened this issue Sep 13, 2020 · 4 comments
Closed

Export produces a non-importable ldif file #3291

389-ds-bot opened this issue Sep 13, 2020 · 4 comments
Labels
closed: fixed Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50232


Issue Description

From BZ:
Description of problem:

A customer is exporting its data with "db2ldif -r" and the ldif has, as first entry, the ruv. The result is that the generated file is not straightfully imported:

entry-id: 1

dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=example,dc=com
objectClass: top
objectClass: nsTombstone
objectClass: extensibleobject
nsUniqueId: ffffffff-ffffffff-ffffffff-ffffffff
nsds50ruv: {replicageneration} 5b4e2610000000010000
nsds50ruv: {replica 1 ldap://example1.example.com:389} 5b4e261000010001000
0 5b4e2610002300010000
nsds50ruv: {replica 2 ldap://example2.example.com:389}
dc: example
nscpEntryDN: dc=example,dc=com
nsruvReplicaLastModified: {replica 1 ldap://example1.example.com:389} 5b4e
2610
nsruvReplicaLastModified: {replica 2 ldap://example2.example.com:389} 0000
0000

entry-id: 2

dn: dc=example,dc=com
objectClass;vucsn-5b4e2610000100010000: domain
objectClass;vucsn-5b4e2610000100010000: top
dc;vucsn-5b4e2610000100010000;mdcsn-5b4e2610000100010000: example
description;vucsn-5b4e2610000100010000: Root of the directory
creatorsName;vucsn-5b4e2610000100010000: cn=directory manager
modifiersName;vucsn-5b4e2610000100010000: cn=directory manager
createTimestamp;vucsn-5b4e2610000100010000: 20180717172328Z
modifyTimestamp;vucsn-5b4e2610000100010000: 20180717172328Z
nsUniqueId: 1e61a805-89e611e8-87c6f971-856b23a3

Version-Release number of selected component (if applicable): 389-ds-base-1.3.7.5-19.el7_5.x86_64

How reproducible: I have not managed to reproduce it yet. Only the customer.

@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the 1.3.9 milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from lkrispen (@elkris) at 2019-02-19 09:21:48

Metadata Update from @elkris:

@389-ds-bot
Copy link
Author

389-ds-bot commented Sep 13, 2020

Comment from vashirov (@vashirov) at 2019-04-02 14:16:31

#3292

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-04-04 17:37:03

Metadata Update from @mreynolds389:

  • Issue set to the milestone: 1.3.9

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-04-04 17:37:11

Metadata Update from @mreynolds389:

  • Issue close_status updated to: fixed
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant