If an upgrade extends or modifies a core schema file this update can be ignored if the definition already exists in 99user.ldif.
The situation can aris if the schema was adhusted during a replication schema comparison.
The fix should have two parts:
Minimize the schema elements in 99user.ldif is related to ticket https://fedorahosted.org/389/ticket/47749
During a replication session if there is a conflict between received definition and current definition, the resolution is to keep or build a definition that is a superset of the received/current and to write it in 99user.ldif
During a client update, there is no control of conflict. The received definition is written in 99user.ldif
Setting target milestone to 1.3.4. If IPA needs it earlier, please feel free to modify it.
thierry bordaz wrote:
This bug also reports a problem that is in https://fedorahosted.org/389/ticket/47749 (target 1.3.3).
Can this ticket be closed as a duplicate of 47749?
Per ticket triage, set milestone to FUTURE.
Metadata Update from @tbordaz: - Issue set to the milestone: FUTURE
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None (was: needinfo) - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1229
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: duplicate)
Login to comment on this ticket.