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
<img alt="0001-Ticket-48006-Missing-warning-for-invalid-replica-bac.patch" src="/389-ds-base/issue/raw/files/cf1cef181ca218da231f86950e1a9f59397e1f7d444422c4c7f55fbd7d3d18ff-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:
<img alt="0001-Ticket-48006-Missing-warning-for-invalid-replica-bac.patch" src="/389-ds-base/issue/raw/files/1cbbb925c688ee8db0c5cd62a8eba157a94237f95258b63b798269a17acaf27a-0001-Ticket-48006-Missing-warning-for-invalid-replica-bac.patch" />
478a2ae..e123acb master -> master
4875300..c7d13c2 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)
<img alt="0001-Issue-48006-Issue-48006-Add-a-new-CI-test-case.patch" src="/389-ds-base/issue/raw/files/718131eb7c624c06deb78f4fb2d834332566002a6dd3804a929355c9b9350dfe-0001-Issue-48006-Issue-48006-Add-a-new-CI-test-case.patch" />
Metadata Update from @aadhikari: - Custom field reviewstatus adjusted to review (was: ack)
<img alt="0001-Issue-48006-Add-a-new-CI-test-case.patch" src="/389-ds-base/issue/raw/files/40375194ae1e3404874cee73ff9af8e6ab56669e085002846eb89f2ef79effcb-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.
<img alt="0001-Issue-48006-Add-a-new-CI-test-case.patch" src="/389-ds-base/issue/raw/files/a14ea79d96c94782df7e729515cf40f3d08b64d201e559d3c2658ef05b0de3e5-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.
<img alt="0001-Issue-48006-Add-a-new-CI-test-case.patch" src="/389-ds-base/issue/raw/files/6bd52e60a0e346a95569f242008dce55b2bb8662aca91548fcb970d18790cb11-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 0f95ada 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.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Log in to comment on this ticket.