| Summary: | 389-ds rejects nsds5ReplicaProtocolTimeout attribute | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Milan Kubík <mkubik> |
| Component: | 389-ds-base | Assignee: | mreynolds |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Sankar Ramalingam <sramling> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | mreynolds, nhosoi, nkinder |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.1.6-14.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Attempt to remove the configuration attribute
Consequence: The operation is rejected.
Fix: Allow the removal of the configuration attribute
Result: Removing of the configuration attribute is successful.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-13 10:00:18 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 918714 | ||
Upstream ticket: https://fedorahosted.org/389/ticket/47620 Found a regression that appears to crash the server. Fixed upstream. In mmrepl/accept for replica: replica_timeout_03 pass for replication agreement: replica_timeout_09 pass $ rpm -qa 389-ds-base 389-ds-base-1.3.1.6-14.el7.x86_64 This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |
Description of problem: The 389 directory server refuses to add nsds5ReplicaProtocolTimeout to either replica entry or replication agreement entry. Version-Release number of selected component (if applicable): 389-ds-base-1.3.1.6-11.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Set up replica on a DS instance. We don't need complete MMR setup for this. 2. Perform ldapmodify to add nsds5ReplicaProtocolTimeout to replica entry. 3. If complete setup is in place, do this on some replication agreement as well. Actual results: Server refuses to add the attribute to the entry. Returns 53 - unwilling to perform. Expected results: The attribute will be added to tyhe entry. Additional info: The attribute is in schema and is listed as allowed attribute in both nsDS5Replica and nsDS5ReplicationAgreement object classes. ---- $ rpm -qa 389-ds-base 389-ds-base-1.3.1.6-11.el7.x86_64 $ grep nsds5ReplicaProtocolTimeout /etc/dirsrv/slapd-s1/schema/01core389.ldif >/dev/null $ echo $? 0 $ cat timeout.ldif dn: cn=24202_to_24206,cn=replica,cn=o\=airius.com,cn=mapping tree,cn=config changetype: modify add: nsds5ReplicaProtocolTimeout nsds5ReplicaProtocolTimeout: 15 - $ ldapmodify -h localhost -p 24202 -D "cn=directory manager" -w Secret123 -f timeout.ldif -v ldap_initialize( ldap://localhost:24202 ) add nsds5ReplicaProtocolTimeout: 15 modifying entry "cn=24202_to_24206,cn=replica,cn=o\=airius.com,cn=mapping tree,cn=config" ldap_modify: Server is unwilling to perform (53) $ cat timeout.ldif dn: cn=replica,cn=o\=airius.com,cn=mapping tree,cn=config changetype: modify add: nsds5ReplicaProtocolTimeout nsds5ReplicaProtocolTimeout: 15 - $ ldapmodify -x -h localhost -p 24202 -D "cn=directory manager" -w Secret123 -f timeout.ldif -v ldap_initialize( ldap://localhost:24202 ) add nsds5ReplicaProtocolTimeout: 15 modifying entry "cn=replica,cn=o\=airius.com,cn=mapping tree,cn=config" ldap_modify: Server is unwilling to perform (53) additional info: modification of attribute nsds5ReplicaProtocolTimeout is not allowed in replica entry