Log output when shadowLastChange is changed on supplier
repl.log

I could not reproduce the problem. My test steps are as follows:

This is my fractional replication setup in the agreement:
{{{
dn: cn=agreement,cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config
nsDS5ReplicatedAttributeList: (objectclass=*) $ EXCLUDE passwordAllowChangeTime passwordExpirationTime
}}}

I created subtree password policy at the suffix level under dc=example,dc=com.

Added passwordAllowChangeTime to the password policy container on Master 1:
{{{
$ ldapmodify -x -h localhost -p -D 'cn=directory manager' -w password
dn: cn=cn\3DnsPwPolicyEntry\2Cdc\3Dexample\2Cdc\3Dcom,cn=nsPwPolicyContainer,dc=example,dc=com
changetype: modify
replace: passwordAllowChangeTime
passwordAllowChangeTime: 20120425120000Z
}}}

Search the attribute value on Master 1 and the attribute-value is returned:
{{{
$ ldapsearch -LLLx -h localhost -p -D 'cn=directory manager' -w password -b 'dc=example,dc=com' "(&(objectclass=ldapsubentry)(objectclass=passwordpolicy))" passwordAllowChangeTime
dn: cn=cn\3DnsPwPolicyEntry\2Cdc\3Dexample\2Cdc\3Dcom,cn=nsPwPolicyContainer,d
c=example,dc=com
passwordAllowChangeTime: 20120425120000Z
}}}

Search the attribute value on Master 2 and the attribute-value is not returned:
{{{
$ ldapsearch -LLLx -h localhost -p -D 'cn=directory manager' -w password -b 'dc=example,dc=com' "(&(objectclass=ldapsubentry)(objectclass=passwordpolicy))" passwordAllowChangeTime
dn: cn=cn\3DnsPwPolicyEntry\2Cdc\3Dexample\2Cdc\3Dcom,cn=nsPwPolicyContainer,d
c=example,dc=com
$
}}}

If it is different from your attempt, please share your reproducer with us.
Thanks.

set default ticket origin to Community

ping - still need info - will close because we cannot reproduce

Added initial screened field value.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/330

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.