#50886 Typo in the replication debug message "error 0 for oparation 561"
Closed: wontfix by mreynolds. Opened by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1772616

Description of problem:
There is a typo in the replication debug message:
    "multimaster_mmr_postop - error 0 for oparation 561."
Version-Release number of selected component (if applicable):
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.8 Beta (Maipo)
# rpm -qa | grep 389-ds-base-1
389-ds-base-1.3.10.1-2.el7.x86_64
#
How reproducible:
Always.
Steps to Reproduce:
1. Enable the replication log level ( nsslapd-errorlog-level: 8192 )
2. Check in the RHDS errors log
Actual results:
    "multimaster_mmr_postop - error 0 for oparation 561."
Expected results:
    "multimaster_mmr_postop - error 0 for operation 561."
Additional info:
This might break customer monitoring scripts.

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1772616

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

Commit d8988cc3 relates to this ticket

Commit d8988cc relates to this ticket

472045a3f..2b6c1bb3f 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

751d8cfd9..9928e5bcb 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

f58f732b0..33bf3e77c 389-ds-base-1.3.10 -> 389-ds-base-1.3.10

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

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.3.10 (was: 0.0 NEEDS_TRIAGE)

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

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