[OPENDJ-3480] Updating schema backend properties while it is enabled leaves schema backend in broken state Created: 10/Nov/16  Updated: 08/Nov/19  Resolved: 08/Nov/18

Status: Done
Project: OpenDJ
Component/s: backends
Affects Version/s: 4.0.0, 3.5.1, 3.5.0
Fix Version/s: 6.5.0

Type: Bug Priority: Minor
Reporter: Ian Packer [X] (Inactive) Assignee: Matthew Swift
Resolution: Fixed Votes: 0
Labels: release-notes

Epic Link: Bugs 6.5
Story Points: 0
Dev Assignee: Matthew Swift
Support Ticket IDs:

 Description   

This looks like a new problem in 3.5.0+

To reproduce:

./setup --ldapPort 1389 -S --adminConnectorPort 14444 -w password -h opendj.example.com --acceptLicense -n
./dsconfig -p 14444 --trustAll -w password -D "cn=Directory Manager" -h opendj.example.com -n set-backend-prop --backend-name schema --set show-all-attributes:true
./ldapsearch -p 1389 -b "cn=schema" -s base "&" 1.1

Result:

SEARCH operation failed
Result Code:  32 (No Such Entry)
Additional Information:  Unable to retrieve the requested entry cn=schema from the schema backend because the DN is equal to one of the schema entry DNs

Expected result:
The cn=schema base entry is returned.

Restarting the server after changing the properties will fix the problem. Another workaround is to use this sequence of commands to change properties (manually taking the backend offline).

./dsconfig -p 14444 --trustAll -w password -D "cn=Directory Manager" -h opendj.example.com -n set-backend-prop --backend-name schema --set enabled:false --set show-all-attributes:true
./dsconfig -p 14444 --trustAll -w password -D "cn=Directory Manager" -h opendj.example.com -n set-backend-prop --backend-name schema --set enabled:true


 Comments   
Comment by Ian Packer [X] (Inactive) [ 10/Nov/16 ]

Also broken in opendj-4.0.0-20161110

Comment by Ludovic Poitou [ 19/Feb/18 ]

This issue seems to have been resolved in DS 6.0.0.
I don't reproduce it with the current master.

Comment by Ludovic Poitou [ 08/Nov/18 ]

This is working fine with 6.5.0.
I believe this was fixed as part of some refactoring and cleanup in backends. Could have happened earlier.

Comment by Matthew Swift [ 07/Nov/19 ]

Moved to closed state because the fixVersion has already been released.

Generated at Fri Oct 23 08:03:00 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.