#51141 Issue 51100 - Correct numSubordinates value for cn=monitor
Closed by spichugi. Opened by spichugi.
spichugi/389-ds-base i51100  into  master

Download 51141.patch

Bug Description: numSubordinates for cn=monitor shows 4
while there are 3 child entries are present.

Fix Description: Ignore easter egg entry while increasing
numSubordinates count.

https://pagure.io/389-ds-base/issue/51100

Reviewed by: ?

I can not find this DN in the source code, where is the easter egg entry coming from?

It's stored obfuscated in easter_egg_entry in fedse.c:

2624        egg_decode(src); /* twiddle bits */
(gdb) 
2625        e = slapi_str2entry(src, 0);
(gdb) p src
$1 = 0x55ba3a5584a0 "dn: ou=Red Hat Directory Server Team,cn=monitor\nobjectClass: top\nobjectClass: organizationalUnit\nobjectClass: directory-team-extensible-object\nou: Netscape Security Solutions\nou: Netscape Directory Te"...

It's stored obfuscated in easter_egg_entry in fedse.c:
2624 egg_decode(src); / twiddle bits /
(gdb)
2625 e = slapi_str2entry(src, 0);
(gdb) p src
$1 = 0x55ba3a5584a0 "dn: ou=Red Hat Directory Server Team,cn=monitor\nobjectClass: top\nobjectClass: organizationalUnit\nobjectClass: directory-team-extensible-object\nou: Netscape Security Solutions\nou: Netscape Directory Te"...

Thanks! Ok, LGTM

rebased onto ac58ddf3e4c3a4f0388c56b262da8f7eeb11e230

Pull-Request has been merged by spichugi

I've never enjoyed a bug report quite so much as this in hindsight :)

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/4194

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

Metadata