Replication not excluding attributes

[Iain Morgan]

Hi,

I recently tried to setup a slave replica using fractional replication.
The slave replica works, but the attributes which I had intended to
exclude are still being replicated.

The replication agreement on the supplier includes:

% ldapsearch -b cn=config '(cn=Slave)' nsds5replicatedattributelist
dn: cn=Slave,...
nsds5replicatedattributelist: (objectClass=*) $ EXCLUDE passwordAllowChangeTim
 e passwordExpirationTime passwordGraceUserTime shadowLastChange passwordHisto
 ry


Are there circumstances where nsds5ReplicatedAttributeList is ignored?

-- 
Iain Morgan

[Rich Megginson]

On 03/27/2012 05:11 PM, Iain Morgan wrote:
>  Hi,
>
>  I recently tried to setup a slave replica using fractional replication.
>  The slave replica works, but the attributes which I had intended to
>  exclude are still being replicated.
>
>  The replication agreement on the supplier includes:
>
>  % ldapsearch -b cn=config '(cn=Slave)' nsds5replicatedattributelist
>  dn: cn=Slave,...
>  nsds5replicatedattributelist: (objectClass=*) $ EXCLUDE passwordAllowChangeTim
>    e passwordExpirationTime passwordGraceUserTime shadowLastChange passwordHisto
>    ry
>
>
>  Are there circumstances where nsds5ReplicatedAttributeList is ignored?
>  
No.  What is your platform and 389-ds-base version?
Can you reproduce the problem with the replication log level set?  
http://port389.org/wiki/FAQ#Troubleshooting

[Iain Morgan]

On Tue, Mar 27, 2012 at 20:07:07 -0500, Rich Megginson wrote:
>  On 03/27/2012 05:11 PM, Iain Morgan wrote:
>  > Hi,
>  >
>  > I recently tried to setup a slave replica using fractional replication.
>  > The slave replica works, but the attributes which I had intended to
>  > exclude are still being replicated.
>  >
>  > The replication agreement on the supplier includes:
>  >
>  > % ldapsearch -b cn=config '(cn=Slave)' nsds5replicatedattributelist
>  > dn: cn=Slave,...
>  > nsds5replicatedattributelist: (objectClass=*) $ EXCLUDE passwordAllowChangeTim
>  >   e passwordExpirationTime passwordGraceUserTime shadowLastChange passwordHisto
>  >   ry
>  >
>  >
>  > Are there circumstances where nsds5ReplicatedAttributeList is ignored?
>  >
>  No.  What is your platform and 389-ds-base version?
>  Can you reproduce the problem with the replication log level set?  
>  http://port389.org/wiki/FAQ#Troubleshooting 
RHEL 6.2 and 389-ds-base-1.2.10.4-1.el6.

I set nsslapd-errorlog-level to 8192 and then changed the
shadowLastChange attribute for an entry. The change was propagated to
the slave replica despite the fact that shadowLastChange is one of the
excluded attributes. I've attached the log output.
-- 
Iain Morgan

[Rich Megginson]

On 03/28/2012 10:08 AM, Iain Morgan wrote:
>  On Tue, Mar 27, 2012 at 20:07:07 -0500, Rich Megginson wrote:
> > On 03/27/2012 05:11 PM, Iain Morgan wrote:
> >> Hi,
> >>
> >> I recently tried to setup a slave replica using fractional replication.
> >> The slave replica works, but the attributes which I had intended to
> >> exclude are still being replicated.
> >>
> >> The replication agreement on the supplier includes:
> >>
> >> % ldapsearch -b cn=config '(cn=Slave)' nsds5replicatedattributelist
> >> dn: cn=Slave,...
> >> nsds5replicatedattributelist: (objectClass=*) $ EXCLUDE passwordAllowChangeTim
> >>    e passwordExpirationTime passwordGraceUserTime shadowLastChange passwordHisto
> >>    ry
> >>
> >>
> >> Are there circumstances where nsds5ReplicatedAttributeList is ignored?
> >>
> > No.  What is your platform and 389-ds-base version?
> > Can you reproduce the problem with the replication log level set?
> > http://port389.org/wiki/FAQ#Troubleshooting
>  RHEL 6.2 and 389-ds-base-1.2.10.4-1.el6.
>
>  I set nsslapd-errorlog-level to 8192 and then changed the
>  shadowLastChange attribute for an entry. The change was propagated to
>  the slave replica despite the fact that shadowLastChange is one of the
>  excluded attributes. I've attached the log output. 
ok - please file a ticket at
https://fedorahosted.org/389