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:
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
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.
Metadata Update from @lkrispen: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1603140
https://pagure.io/389-ds-base/pull-request/50233
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.9
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3291
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.