389-ds-base

#48380 SynRepl does not handle database re-initialization properly
Closed: wontfix by mreynolds. Opened by pspacek.

Closed: wontfix
Reopen Issue

SynRepl plugin does not handle database re-initialization properly:

  • clients which are connected during re-init do not get new/changed entries at all
  • the synchronization cookie contains changeNumber from retro change log which does not make sense after database re-init. Old cookies (pre-dating re-init) should be recognized as invalid.

there is no mechanism yet for a plugin to detect if a database was reimported, this should be provided by a fix for #48402

Resetting the milestone to NEEDS_TRIAGE.

Metadata Update from @lkrispen:
- Issue assigned to lkrispen
- Issue set to the milestone: 1.3.6.0

Metadata Update from @mreynolds:
- Custom field component reset (from Server - Plugins)
- Issue close_status updated to: None
- Issue set to the milestone: 1.3.7 backlog (was: 1.3.6.0)

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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

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)
Metadata
None
None
None
Normal
IPA
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.