https://bugs.openldap.org/show_bug.cgi?id=10086
Issue ID: 10086 Summary: test059 does not set up valid cn=config replication Product: OpenLDAP Version: 2.6.4 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: test suite Assignee: bugs@openldap.org Reporter: quanah@openldap.org Target Milestone: ---
For cn=config replication to be valid, the entryUUIDs must match throughout the config database. However, this is not the case when test059 executes. The entryUUID for 'dn: cn=config' differs between the two.
Example:
quanah@apito1:~/git/quanah/openldap-scratch/tests/testrun$ grep entryUUID: cfcon.d/cn=config.ldif entryUUID: aea058c4-bf6e-103d-9e18-4582986e9372 quanah@apito1:~/git/quanah/openldap-scratch/tests/testrun$ grep entryUUID: db.1.a/cn=config,cn=consumer.ldif entryUUID: ae9bd858-bf6e-103d-871e-5daccf782d22
https://bugs.openldap.org/show_bug.cgi?id=10086
--- Comment #1 from Ondřej Kuzník ondra@mistotebe.net --- You can't reasonably expect the starting uuids to match in a situation like that. The consumers need cn=config to start a syncrepl session and those need their uuids generated before it even contemplates making contact.
But there is definitely an issue with test059 and test086, since cn=config,cn=consumer also holds a cn: consumerconfig value, not something cn=config is willing to receive at this point.
https://bugs.openldap.org/show_bug.cgi?id=10086
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs_review | Target Milestone|--- |2.7.0 Assignee|bugs@openldap.org |quanah@openldap.org
https://bugs.openldap.org/show_bug.cgi?id=10086
Howard Chu hyc@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|2.7.0 |2.7.1
-
openldap-its＠openldap.org