[OPENDJ-6216] Ldapsearch returns different results when DJ upgraded and different when just installed Created: 16/Apr/19  Updated: 08/Nov/19  Resolved: 03/May/19

Status: Done
Project: OpenDJ
Component/s: upgrade
Affects Version/s: 7.0.0
Fix Version/s: Not applicable

Type: Bug Priority: Major
Reporter: Michal Severin Assignee: Matthew Swift
Resolution: Not a defect Votes: 0
Labels: None
Environment:

Found on Linux, OpenDJ 7.0.0-SNAPSHOT rev. 5a25b0834dc


Epic Link: Bugs 7.0
Story Points: 0.5

 Description   

Different number of results is returned when DJ is upgraded - cn=myself is missing. When DJ is installed and not upgraded cn=myself is found

Steps

1. Install DJ (7.0.0) and check number of entries

ldapsearch -h pyforge.example.com -p 1389 -D "cn=Directory Manager" -w password -b "" --countEntries "(objectclass=*)" dn

2. Install DJ (4.0.0) and upgrade to 7.0.0 and check number of entries

ldapsearch -h pyforge.example.com -p 1389 -D "cn=Directory Manager" -w password -b "" --countEntries "(objectclass=*)" dn

 3. Compare number of entries without and with upgrade

To reproduce:

./run-pybot.py -s clu_group.LdapSearch_DJ -t Check_Default_Basedn opendj

Expected result:

Both ldapsearch with and without upgrade should find cn=myself and same number of entries.

Actual result:
Entries found without upgrade

Total number of matching entries: 1083

Entries found with upgrade - cn=myself is missing

Total number of matching entries: 1082


 Comments   
Comment by Matthew Swift [ 03/May/19 ]

This behavior is expected. It's because upgrade does not automatically make the root user a public backend, which is now the case for new installs.

More generally, the goal of upgrade is to ensure that there are no behavioral differences before and after upgrade. Typically this means making configuration changes or re-indexing databases so that the server continues to work after upgrade. On the other hand, no attempt is made to enable new features or to otherwise make the server behave as if it were a new install. To put it another way, an end-user should be able to safely perform an upgrade without worrying about whether the server will continue to be compatible with their existing client applications, security policies, etc.

Comment by Michal Severin [ 07/May/19 ]

Thank you for info, I did not know that. I will close the issue.

Generated at Mon Sep 21 15:35:43 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.