RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1561769 - [RFE] revise the "transient error" message in a replication agreement's last update status
Summary: [RFE] revise the "transient error" message in a replication agreement's last ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: 7.7
Assignee: mreynolds
QA Contact: RHDS QE
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-28 21:41 UTC by mreynolds
Modified: 2021-04-16 14:35 UTC (History)
7 users (show)

Fixed In Version: 389-ds-base-1.3.9.1-1.el7
Doc Type: Enhancement
Doc Text:
.The `replicaLastUpdateStatusJSON` status attribute has been added to replication agreements in Directory Server This update introduces the `replicaLastUpdateStatusJSON` status attribute to the `cn=<replication_agreement_name>,cn=replica,cn=<suffix_DN>,cn=mapping tree,cn=config` entry. The status displayed in the `replicaLastUpdateStatus` attribute was vague and unclear. The new attribute provides a clear status message and result code and can be parsed by other applications that support the JSON format.
Clone Of:
Environment:
Last Closed: 2019-08-06 12:58:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2152 0 None None None 2019-08-06 12:58:42 UTC

Description mreynolds 2018-03-28 21:41:29 UTC 
Description of problem:

During replication an agreement for various reasons can not send updates to its consumer.  That consumer might be in a a replication session with a different master, etc.  But in the last update status of a replication agreement we see for example: 

"Error (18) Replication error acquiring replica: Incremental update transient error. Backing off, will retry update later. (transient error)"

The "transient error" text can be confusing, as this is not a severe condition.  It should be changed to "transient warning", or something less alarming than "error".
Comment 5 bsmejkal 2019-05-16 07:05:33 UTC 
Build tested:
ipa-server-4.6.5-8.el7.x86_64
389-ds-base-1.3.9.1-6.el7.x86_64


# ipa-replica-manage list -v server.example.com
Directory Manager password: 

server2.example.com: replica
  last init status: Error (0) Total update succeeded
  last init ended: 2019-05-14 07:45:05+00:00
  last update status: Error (0) Replica acquired successfully: Incremental update succeeded
  last update ended: 2019-05-14 09:04:13+00:00

server3.example.com: replica
  last init status: Error (18) Total update succeeded
  last init ended: 2019-05-14 07:45:05+00:00
  last update status: Error (18) Replication error acquiring replica: 
Incremental update transient warning.  Backing off, will retry update later. (transient warning)
  last update ended: 2019-05-14 09:04:13+00:00


Marking as VERIFIED, SanityOnly.
Comment 9 errata-xmlrpc 2019-08-06 12:58:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2152
Comment 10 Jan Gerrit Kootstra 2021-04-16 14:35:17 UTC 
RHEL 7.9, ipa-server-4.6.8-5.el7.x86_64 and 389-ds-base-1.3.10.2-9.el7_9.x86_64 show the original error message:

/usr/bin/repl-monitor.pl -s -f /root/repl-monitor.conf
Directory Server Replication Status (Version 1.1)

Time: Fri Apr 16 2021 16:25:57

Supplier: ipa-server1.example.com:389
------------------------------------
Replica Root: dc=example,dc=com
Replica ID: 4
Max CSN: 60799e98000000040000 (04/16/2021 16:26:32)
-
Consumer: ipa-server1.example.com:389 ldap://ipa-server1.example.com:389/
Type: Unavailable
Time Lag: n/a
Supplier Max CSN: Unavailable
Consumer Max CSN: Unavailable
Last Modify Time: Unavailable
Supplier: ipa-server1.example.com:389
Sent/Skipped: 27 / 144100
Update Status: Error (0) Replica acquired successfully: Incremental update started
Update Started: 04/16/2021 16:25:57
Update Ended: 01/01/1970 01:00:00
Schedule: always in sync
SSL: SASL/GSSAPI
-
Consumer: ipa-server2.example.com:389 ldap://ipa-server2.example.com:389/
Type: Unavailable
Time Lag: n/a
Supplier Max CSN: Unavailable
Consumer Max CSN: Unavailable
Last Modify Time: Unavailable
Supplier: ipa-server1.example.com:389
Sent/Skipped: 28 / 141674
Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
Update Started: 04/16/2021 16:25:32
Update Ended: 04/16/2021 16:25:32
Schedule: always in sync
SSL: SASL/GSSAPI
-
Consumer: ipa-server3.example.com:389 ldap://ipa-server3.example.com:389/
Type: Unavailable
Time Lag: n/a
Supplier Max CSN: Unavailable
Consumer Max CSN: Unavailable
Last Modify Time: Unavailable
Supplier: ipa-server1.example.com:389
Sent/Skipped: 29 / 140321
Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
Update Started: 04/16/2021 16:25:32
Update Ended: 04/16/2021 16:25:32
Schedule: always in sync
SSL: SASL/GSSAPI

Replica Root: o=ipaca
Replica ID: 96
Max CSN: 60799d9f000000600000 (04/16/2021 16:22:23)
-
Consumer: ipa-server1.example.com:389 ldap://ipa-server1.example.com:389/
Type: Unavailable
Time Lag: n/a
Supplier Max CSN: Unavailable
Consumer Max CSN: Unavailable
Last Modify Time: Unavailable
Supplier: ipa-server1.example.com:389
Sent/Skipped: 0 / 0
Update Status: Error (18) Replication error acquiring replica: Incremental update transient warning.  Backing off, will retry update later. (transient warning)
Update Started: 01/01/1970 01:00:00
Update Ended: 01/01/1970 01:00:00
Schedule: always in sync
SSL: SASL/GSSAPI
-
Consumer: ipa-server2.example.com:389 ldap://ipa-server2.example.com:389/
Type: Unavailable
Time Lag: n/a
Supplier Max CSN: Unavailable
Consumer Max CSN: Unavailable
Last Modify Time: Unavailable
Supplier: ipa-server1.example.com:389
Sent/Skipped: 0 / 0
Update Status: Error (18) Replication error acquiring replica: Incremental update transient warning.  Backing off, will retry update later. (transient warning)
Update Started: 01/01/1970 01:00:00
Update Ended: 01/01/1970 01:00:00
Schedule: always in sync
SSL: SASL/GSSAPI
-
Consumer: ipa-server3.example.com:389 ldap://ipa-server3.example.com:389/
Type: Unavailable
Time Lag: n/a
Supplier Max CSN: Unavailable
Consumer Max CSN: Unavailable
Last Modify Time: Unavailable
Supplier: ipa-server1.example.com:389
Sent/Skipped: 0 / 0
Update Status: Error (18) Replication error acquiring replica: Incremental update transient warning.  Backing off, will retry update later. (transient warning)
Update Started: 01/01/1970 01:00:00
Update Ended: 01/01/1970 01:00:00
Schedule: always in sync
SSL: SASL/GSSAPI
Note You need to log in before you can comment on or make changes to this bug.