#51033 Add "time skew fix" to our CLI
Closed: wontfix 3 years ago by spichugi. Opened 4 years ago by mreynolds.

Issue Description

https://www.port389.org/docs/389ds/howto/howto-fix-and-reset-time-skew.html

This process to clean up excessive clock skew is complicated and can be easily messed up. We have the lib389 framework to perform the exact tasks as described on the wiki page, so we should add this "task" to dsctl.

The process...

Master

  • Export Suffix without replication metadata
  • Edit dse.ldif
    • Remove "nsState" attribute from suffix's replication config entry, but not "cn=uniqueid generator,cn=config" or another suffix's nsState attribute.
    • Remove "nsds50ruv" attributes from suffix's replication agreements
  • Import clean LDIF
  • Export LDIF with replication metadata

Replicas

  • Edit dse.ldif
    • Remove "nsState" attribute from suffix's replication config entry, but not "cn=uniqueid generator,cn=config"
    • Remove "nsds50ruv" attributes from the suffix's agreements (if any)
  • Import Replication LDIF

CLI Requirements

  • Handle single or multiple suffixes
  • Handle "first replica" and the "remaining replicas"
  • Options to perform individual steps (only clean dse.ldif, etc)

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: major
- Issue set to the milestone: 1.4.1

3 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.3 (was: 1.4.1)

3 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/4086

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
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata