Re: Possible bug in meta backend??

[Anibal Caceres Hernando <anibal.caceres@ericsson.com>]

   Hi,
   Thank you Pierangelo, I filed an ITS some days ago (number 2935), 
but with the same information as in my message to this list, so I'll try 
to add the way to reproduce to problem to the ITS, and the way I've 
solved it in the code.

Pierangelo Masarati wrote:

> I think this needs some investigation, so I suggest you file
> an ITS.  If you can provide an example of the faulty behavior,
> this could be of help in tracing down the problem and in
> testing if changes do fix it.  In general, back-meta tries to
> do its best to narrow operations to the minimum number of
> targets; this partially explains the "strange" loop you see
> there.  If a target is searched with a DN it cannot contain
> (e.g. a search for "ou=People,dc=example,dc=com" in a target
> whose suffix is "ou=Groups,dc=example,dc=com") that's
> a harmless error; it should be fixed, but it does no bad
> (except if the target replies with a referral, of course :)
>  
   I think the case is that one: a target is searched with a DN it 
doesn't contain, and I agree with you it's harmless, but as it can be 
easily fixed I think it should be... I didn't check if the error still 
happens with 2.2, but I've cheked that portion of code in 2.2.4 and it's 
exactly the same as in 2.1.25, so I  supposse the error is there, but 
I'll try to reproduce it as you suggest me, just to be sure.
   Thank you very much.
   Kind regards,

   Aníbal.