Cause: The directory server runs some operations as triggered by update operations. For example, updating memberof attributes in user entries is triggered by adding a member to a group entry. This updating is done after the original operation. In older versions of directory server, this updating was done outside the original transaction and potentially after sending the result to the client.
Consequence: The client would assume all of the triggered operations were complete after the server returned the response. The client would then expect to see data that wasn't actually there.
Fix: The directory server has been modified so that all of the triggered operations are done inside the same transaction as the original request. All of the triggered operations are complete before the response is sent to the client.
Result: The client expects and sees a consistent view of the data in the directory server.