What were you trying to do that didn't work?

Replication was failing because of missing changes in the changelogs.

What is the impact of this issue to you?

Replication failure was causing issue with customer users.

Please provide the package NVR for which the bug is seen:

cat etc/redhat-release 
Red Hat Enterprise Linux release 9.4 (Plow)

grep ^389-ds installed-rpms 
389-ds-base-2.4.5-7.module+el9dsrv+22137+7a1133f7.x86_64    Tue Nov 19 12:12:25 2024
389-ds-base-libs-2.4.5-7.module+el9dsrv+22137+7a1133f7.x86_64 Tue Nov 19 12:12:24 2024

How reproducible is this bug?:

Always

Steps to reproduce

1. Configure replication between 2 suppliers
2. Set the maxage without the duration specifier
3. Reinitialize the peer replica
4. Wait for a few minute and make a change
5. Replication will fail to propagate the new change

For instance:

dsconf <INSTANCE> replication set-changelog --suffix dc=example,dc=com --max-age "10"
Successfully updated replication changelog

dsconf <INSTANCE> replication get-changelog --suffix dc=example,dc=com | grep -i age
nsslapd-changelogmaxage: 10

Expected results

Working replication.

Actual results

Replication is halting.