Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-67008

Some replication status data are reset upon a restart.

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • rhel-9.6
    • rhel-8.10
    • 389-ds-base
    • None
    • 389-ds-base-2.6.1-1.el9
    • No
    • Moderate
    • ZStream
    • rhel-idm-ds
    • Bug Fix
    • Hide
      .Consumer status in a replication agreement on a supplier is displayed correctly after the Directory Server restart

      Before this update, on a supplier in a replication topology, the status of the consumer in a replication agreement was reset during the Directory Server restart. As a result, the displayed consumer initialization time and the replication status were incorrect.

      With this update, the replication agreement entry displays the correct status of the consumer and when it was initialized.
      Show
      .Consumer status in a replication agreement on a supplier is displayed correctly after the Directory Server restart Before this update, on a supplier in a replication topology, the status of the consumer in a replication agreement was reset during the Directory Server restart. As a result, the displayed consumer initialization time and the replication status were incorrect. With this update, the replication agreement entry displays the correct status of the consumer and when it was initialized.
    • Done
    • None

      Description of a problem

      The values of the attributes nsds5replicaLastInitStart and nsds5replicaLastInitEnd are reset to 19700101000000Z after restating the RHDS instance.

      Version-Release number of the selected component

      rpm -q 389-ds-base cockpit-389-ds

      389-ds-base-1.4.3.37-10.module+el8dsrv+21971+f7435891.x86_64
cockpit-389-ds-1.4.3.37-10.module+el8dsrv+21971+f7435891.noarch

      Browser (if applicable)

       

      Steps to reproduce

      1. Create a replication agreement between a supplier and a consumer
2. Reinitialize the consumer
3. Check the values of nsds5replicaLastInitStart and nsds5replicaLastInitEnd
4. Restart the supplier
5. Check again the values. They are now reset to epoch ( 19700101000000Z )

      Actual results

      Replication status information is incorrect.

      Expected results

      Keep the values of the last initialization start and end.

      Additional information

      Customers might think that the previous reinitialization actually failed and would attempt to redo it again and again.

       

              tbordaz@redhat.com Thierry Bordaz
              rhn-support-tmihinto Têko Mihinto
              IdM DS Dev IdM DS Dev
              Sumedh Sidhaye Sumedh Sidhaye
              Evgenia Martyniuk Evgenia Martyniuk
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: