#47836 Do not return '0' as empty fallback value of nsds5replicalastupdatestart and nsds5replicalastupdatestart
Closed: wontfix None Opened 9 years ago by tbabej.

Search for replication related attrs nsds5replicalastupdatestart and nsds5replicalastupdateend returns '0' if these attributes have no value set.

However, syntax of these attributes is LDAP Generalized time, and '0' is not a valid LDAP Generalized time value.


nsds5replicaLastInitStart and nsds5replicaLastInitEnd are also affected.

Reviewed by Mark (Thank you!!)

Pushed to master:
dbb5ef5..ed0a504 master -> master
commit ed0a504

Pushed to 389-ds-base-1.3.3:
3520ab8..07cd61f 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 07cd61f

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.3 backlog

7 years ago

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/1167

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

3 years ago

Login to comment on this ticket.

Metadata