Upgrading from 1.2.2-1.el5 to 1.2.9.9-1.el5 deletes userRoot

[389-ds-bot]

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

• Created at 2012-01-04 18:42:22 by mkosek
• Closed as Invalid
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=770705

---

https://bugzilla.redhat.com/show_bug.cgi?id=770705

Upgrade 389-ds-base from 1.2.2-1.el5 to 1.2.9.9-1.el5.

The server refuses to start, the error log complains:

[28/Dec/2011:06:24:16 -0600] - nsslapd-subtree-rename-switch is on, while the
in
stance userRoot is in the DN format. Please run dn2rdn to convert the database
format.
[28/Dec/2011:06:24:16 -0600] - nsslapd-subtree-rename-switch is on, while the
instance NetscapeRoot is in the DN format. Please run dn2rdn to convert the
databa
se format.[28/Dec/2011:06:24:16 -0600] - start: Failed to start databases,
err=-1 Unknown
error: -1[28/Dec/2011:06:24:16 -0600] - Failed to start database plugin ldbm
database[28/Dec/2011:06:24:16 -0600] - WARNING: ldbm instance userRoot already
exists
[28/Dec/2011:06:24:16 -0600] - WARNING: ldbm instance NetscapeRoot already
exists

Discover that dn2rdn is called from setup-ds.pl, so we run "setup-ds.pl -u". No
idea why the RPM postinstall script doesn't "do the right thing".

We run "setup-ds.pl -u" and it emits thousands of warnings, one for each entry
in the database:

[28/Dec/2011:06:37:16 -0600] - userRoot: WARNING: skipping an entry with a
corrupted dn (syntax value): zzz0107A (id 63863)
[28/Dec/2011:06:37:16 -0600] - userRoot: WARNING: skipping an entry with a
corrupted dn (syntax value): zzz  MS E (id 63864)
[28/Dec/2011:06:37:16 -0600] - userRoot: WARNING: skipping an entry with a
corrupted dn (syntax value): zzz0111A (id 63865)
[28/Dec/2011:06:37:16 -0600] - userRoot: WARNING: skipping an entry with a
corrupted dn (syntax value): zzz  DR I (id 63866)

At the end up the upgrade process, the database is completely empty, all data
has been destroyed.

The message "skipping an entry with a corrupted dn (syntax value)" is too vague
to be useful - it doesn't say what DN, it doesn't say what syntax value, so I'm
in the dark as what action to take.

[389-ds-bot]

Comment from rmeggins (@richm) at 2012-01-10 06:05:46

batch update to FUTURE milestone

[389-ds-bot]

Comment from nkinder (@nkinder) at 2012-08-28 04:14:23

Added initial screened field value.

[389-ds-bot]

Comment from rmeggins (@richm) at 2017-02-11 22:57:53

Metadata Update from @richm:

• Issue set to the milestone: N/A