389-ds-base

#48006 Missing warning for invalid replica backoff configuration
Closed: wontfix Opened by nhosoi.

Closed: wontfix
Reopen Issue 
Description of a problem:
In the scenario where attributes nsds5ReplicaBackoffMin >
nsds5ReplicaBackoffMax were set using dse.ldif, an error/warning is logged to
indicate the inconsistency only on the server startup. It should be logged when
configuration is performed using cn=config as well.
Steps to Reproduce:
1. Set up a replica
2. Configure nsds5ReplicaBackoffMin > nsds5ReplicaBackoffMax using cn=config.
Actual results:
The warning is not logged.
Expected results:
The warning is logged.
[23/Jan/2015:15:37:48 +0100] NSMMReplicationPlugin - Backoff minimum (10) can
not be greater than the backoff maximum (3).  Using default values: min (3) max
(300)

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

Metadata Update from @mreynolds:
- Custom field component reset (from Replication - General)
- Issue close_status updated to: None
- Issue set to the milestone: 1.3.7.0 (was: 1.3.6.0)

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

0001-Ticket-48006-Missing-warning-for-invalid-replica-bac.patch

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field reviewstatus adjusted to review
- Custom field version adjusted to None

 
26 +                        PRUint64 max;

Can we make this uint64_t max = 0; ?

Otherwise I'm happy with it :) ack from me,

Can we make this uint64_t max = 0; ?
Otherwise I'm happy with it :) ack from me,

Done:

0001-Ticket-48006-Missing-warning-for-invalid-replica-bac.patch

478a2aebd..e123acb69 master -> master

487530050..c7d13c29a 389-ds-base-1.3.7 -> 389-ds-base-1.3.7

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to ack (was: review)
- Issue tagged with: RFE

Metadata Update from @mreynolds:
- Issue untagged with: RFE
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

0001-Issue-48006-Issue-48006-Add-a-new-CI-test-case.patch

Metadata Update from @aadhikari:
- Custom field reviewstatus adjusted to review (was: ack)

0001-Issue-48006-Add-a-new-CI-test-case.patch

Can you rebase to master and check again? The repl patch has merged,

@firstyear sure, I have uploaded this patch much before our chat on the channel, so was unaware of it.

0001-Issue-48006-Add-a-new-CI-test-case.patch

This looks good, but can you reset the config too? Should be something like:

replica.remove('attr')

Should trigger the default value to be reapplied at the end.

0001-Issue-48006-Add-a-new-CI-test-case.patch
@firstyear something like this?

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to ack (was: review)

commit 0f95ada946fd6aeb1a4bb5168034a474aebd790b
Author: Akshay Adhikari aadhikar@aadhikar.pnq.csb
Date: Thu Jan 18 18:16:16 2018 +0530

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

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
None
None
None
Normal
QE
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.