Bug 1086890

Summary: empty modify returns LDAP_INVALID_DN_SYNTAX
Product: Red Hat Enterprise Linux 7 Reporter: Noriko Hosoi <nhosoi>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: low    
Version: 7.1CC: nkinder, rmeggins, vashirov
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.3.1-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1086889 Environment:
Last Closed: 2015-03-05 09:34: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:
Embargoed:

Description Noriko Hosoi 2014-04-11 18:37:35 UTC 
Description of problem:
Doing an empty modify operation returns LDAP_INVALID_DN_SYNTAX to the client. It should be allowed with no errors.

Version-Release number of selected component (if applicable):


How reproducible:
ldapbertest

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Viktor Ashirov 2014-12-01 16:54:16 UTC 
$ rpm -qa  | grep 389
389-ds-base-1.3.3.1-9.el7.x86_64
389-ds-base-debuginfo-1.3.3.1-9.el7.x86_64
389-ds-base-libs-1.3.3.1-9.el7.x86_64

I ran ldapbertest, here's the output from testcases 83 and 84: 

Executing test test083ModifyNoMods

Completed test test083ModifyNoMods
######################################################################
tp083: expect=0 actual=0
PASS
######################################################################

Executing test test084ModifyEmptyMods

Completed test test084ModifyEmptyMods
######################################################################
tp084: expect=0 actual=0
PASS
######################################################################

Hence marking as VERIFIED.
Comment 4 errata-xmlrpc 2015-03-05 09:34:18 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0416.html