test050-syncrepl-multimaster fails on 2.4.39/mdb

[Jean Gillaux <jgillaux@webbfontaine.com>]

Hello,

When running test suite for openldap 2.4.39, I see
test050-syncrepl-multimaster failing with mdb.
Software is build with ./configure --enable-overlays
Env is: lxc container 0.9.0.alpha3 running debian wheezy, gcc version
4.7.2 (Debian 4.7.2-5)

Same test with hdb is ok.


Here is test output:
Cleaning up test run directory leftover from previous run.
Running ./scripts/test050-syncrepl-multimaster for mdb...
running defines.sh
Initializing server configurations...
Starting server 1 on TCP/IP port 9011...
Using ldapsearch to check that server 1 is running...
Inserting syncprov overlay on server 1...
Starting server 2 on TCP/IP port 9012...
Using ldapsearch to check that server 2 is running...
Configuring syncrepl on server 2...
Starting server 3 on TCP/IP port 9013...
Using ldapsearch to check that server 3 is running...
Configuring syncrepl on server 3...
Starting server 4 on TCP/IP port 9014...
Using ldapsearch to check that server 4 is running...
Configuring syncrepl on server 4...
Adding schema and databases on server 1...
Using ldapadd to populate server 1...
Waiting 15 seconds for syncrepl to receive changes...
Using ldapsearch to read config from server 1...
Using ldapsearch to read config from server 2...
Using ldapsearch to read config from server 3...
Using ldapsearch to read config from server 4...
Comparing retrieved configs from server 1 and server 2...
Comparing retrieved configs from server 1 and server 3...
Comparing retrieved configs from server 1 and server 4...
Using ldapsearch to read all the entries from server 1...
Using ldapsearch to read all the entries from server 2...
Using ldapsearch to read all the entries from server 3...
Using ldapsearch to read all the entries from server 4...
Comparing retrieved entries from server 1 and server 2...
test failed - server 1 and server 2 databases differ

The diff between 1 and 2 is:
363,388d362
< dn: cn=Manager,dc=example,dc=com
< objectClass: person
< cn: Manager
< cn: Directory Manager
< cn: Dir Man
< sn: Manager
< description: Manager of the directory
< userPassword:: c2VjcmV0
<
< dn: cn=Mark Elliot,ou=Alumni Association,ou=People,dc=example,dc=com
< objectClass: OpenLDAPperson
< cn: Mark Elliot
< cn: Mark A Elliot
< sn: Elliot
< uid: melliot
< postalAddress: Alumni Association $ 111 Maple St $ Anytown, MI 48109
< seeAlso: cn=All Staff,ou=Groups,dc=example,dc=com
< homePostalAddress: 199 Outer Drive $ Ypsilanti, MI 48198
< homePhone: +1 313 555 0388
< drink: Gasoline
< title: Director, UM Alumni Association
< mail: melliot@mail.alumni.example.com
< pager: +1 313 555 7671
< facsimileTelephoneNumber: +1 313 555 7762
< telephoneNumber: +1 313 555 4177
<
395,409d368
<
< dn: cn=Ursula Hampster,ou=Alumni Association,ou=People,dc=example,dc=com
< objectClass: OpenLDAPperson
< cn: Ursula Hampster
< sn: Hampster
< uid: uham
< title: Secretary, UM Alumni Association
< postalAddress: Alumni Association $ 111 Maple St $ Anytown, MI 48109
< seeAlso: cn=All Staff,ou=Groups,dc=example,dc=com
< homePostalAddress: 123 Anystreet $ Anytown, MI 48104
< mail: uham@mail.alumni.example.com
< homePhone: +1 313 555 8421
< pager: +1 313 555 2844
< facsimileTelephoneNumber: +1 313 555 9700
< telephoneNumber: +1 313 555 5331

Do you have any suggestion regarding this?
Thanks

-- 

Jean