[Date Prev][Date Next] [Chronological] [Thread] [Top]

(ITS#5809) syncrepl + back-ldif + "rename to same DN" fails



Full_Name: Hallvard B Furuseth
Version: HEAD
OS: Linux
URL: 
Submission from: (NULL) (129.240.6.233)
Submitted by: hallvard


With the latest back-ldif/ldif.c (rev 1.99),
	./run -b ldif test048-syncrepl-multiproxy
breaks with "master and P1 slave databases differ" and
	./run -b ldif test018-syncreplication-persist
when patched to not reject $BACKEND = ldif
breaks with "producer and consumer databases differ".

The offender is "rename to same DN" (ITS#5319), i.e. rev 1.99.
Unless there is a big "duh!" in it, it exposed a syncrepl bug.

It's unrelated to the other recent back-ldif patches: 1.98 passes
these tests, as does 1.87, while 1.87 + a "rename to same DN" patch
breaks.  Rev 1.99 passes test005-modrdn & test040-subtree-rename.


Another strange thing I've seen recently is that bash
once in a while complains something like
	./scripts/test018-syncreplication-persist:
	line 361: echo: write error: Interrupted system call
This is indeed just an "echo" statement in the test script:
	echo "Comparing retrieved entries from producer and consumer..."
Don't know what's going on or if it's relatead, but I've
not seen (or noticed) it before.