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 1478900 - please change the replication transient status Err=18 into a warning.
Summary: please change the replication transient status Err=18 into a warning.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-07 13:13 UTC by German Parente
Modified: 2020-09-10 11:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-12 19:32:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description German Parente 2017-08-07 13:13:23 UTC
Description of problem:

This is simple fix asked to convert the transient replication status (18) that is happening when replica is locked into a warning.

It's just that it's confusing for customers.

Comment 2 mreynolds 2017-10-12 19:32:15 UTC
Closing as won't fix.

I thought this bug was for an errors log message that needed to have the severity level adjusted, but after reviewing the customer case this is actually about the replication agmt status attribute "nsds5replicaLastUpdateStatus".

The replication status always uses "Error (%d) msg" format.  "0" for success, or greater than zero for some type of replication state/error.  There is no turning this into a warning - it's just a status code value.  

I also see nothing wrong with the content of the status message (an error occurred, it was not fatal, so it will retry):

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


Note You need to log in before you can comment on or make changes to this bug.