#48420 change severity of some messages related to "keep alive" entries
Closed: wontfix None Opened 6 years ago by lkrispen.

When a keepalive entry cannot be created because it already exists, this should not be logged as an error

The report refers to this message:

NSMMReplicationPlugin - replication keep alive entry <cn=repl keep alive 3,dc=gjn,dc=xxx> already exists

internal bz# 1313258 - change severity of some messages related to "keep alive" entries

(for a reason I cannot modify this ticket to change the "Red Hat Bugzilla" field).

Counting objects: 13, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 959 bytes, done.
Total 7 (delta 5), reused 0 (delta 0)
To ssh://git.fedorahosted.org/git/389/ds.git
2aa0be7..6788445 master -> master

commit 6788445
Author: Thierry Bordaz tbordaz@redhat.com
Date: Tue Mar 1 11:14:54 2016 +0100

Pushed to 389-ds-base-1.3.4:
4a8432c..17bb068 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
commit 17bb068

Pushed to 389-ds-base-1.3.3:
7703649..50405f8 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 50405f8

Pushed to 389-ds-base-1.2.11:
70e6c01..2e30d12 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 2e30d12

Metadata Update from @nhosoi:
- Issue assigned to tbordaz
- Issue set to the milestone:

5 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/1751

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)

2 years ago

Login to comment on this ticket.