Bug 1240405

Summary:	Allow mod_post to consider existing objects for addition to MEP
Product:	Red Hat Enterprise Linux 7	Reporter:	Noriko Hosoi <nhosoi>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED NOTABUG	QA Contact:	Viktor Ashirov <vashirov>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	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:	2015-07-06 23:16:23 UTC	Type:	---
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 2015-07-06 20:13:55 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/48140

MEP expects that the only time it will create a managed entry is on the addition of the entry. Modifying an existing entry and then having it retrospectively add the managed entry is not supported.

Currently, if one creates an object such as:

objectClass: top
objectClass: account
uid: foo
sn: bar

Followed by a mod operation to add posixAttributes, in a standard MEP with user -> group template, the group is not created, because the operation isn't considered unless it's an add.

This attached patch adds support and dynamic plugin tests to allow MEP to create managed entries if a mod operation would bring an entry into a state where it now satisfies the criteria of the template.