Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1081251

Summary: Unable to set nsds5ReplicaBackoffMin or nsds5ReplicaBackoffMax
Product: Red Hat Enterprise Linux 7 Reporter: Michael Gregg <mgregg>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED DUPLICATE QA Contact: Sankar Ramalingam <sramling>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: nkinder, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-26 21:49:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Gregg 2014-03-26 21:28:17 UTC
Description of problem:
receiving "DSA is unwilling to perform" when attempting to set nsds5ReplicaBackoffMin and nsds5ReplicaBackoffMax

I am attempting to set these values as per: http://port389.org/wiki/Design/Replication_Retry_Settings

Version-Release number of selected component (if applicable):
389-ds-base-1.3.1.6-24.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create two servers with replication
2. My replicated cn is cn=ou=my_ou_2,o=my_suffix.com
3. Attempt to set either of these values with a ldap modify similar to:
/usr/lib64/mozldap/ldapmodify -h blade04.idm.lab.eng.rdu2.redhat.com -p 38000 -D "cn=directory manager" -w <password>  << EOF
dn: cn=M1M2,cn=replica,cn=ou\=my_ou_2\,o\=my_suffix.com,cn=mapping tree,cn=config
changetype: modify
replace: nsds5ReplicaBackoffMax
nsds5ReplicaBackoffMax: 30
EOF

Actual results:
modifying entry cn=M1M2,cn=replica,cn=ou\=my_ou_2\,o\=my_suffix.com,cn=mapping tree,cn=config
ldap_modify: DSA is unwilling to perform

Additional info: 
I am attempting to set nsds5ReplicaBackoffMax higher than nsds5ReplicaBackoffMin

Comment 2 Nathan Kinder 2014-03-26 21:49:56 UTC

*** This bug has been marked as a duplicate of bug 1064986 ***