When the schema is replicated, the new schema goes in 99user.ldif. The problem is that the new schema also contains the standard LDAP schemas so we have some duplicated definition in 99user.ldif and for example 00core.ldif
Step to reproduce:
attachment ticket47749_test.py
test case attached (using lib389)
Hi Thierry, do you think this ticket should be fixed for 1.3.2? Or can the target be set to some time later?
Hi Noriko, I do not think it needs to be fixed in 1.3.2. Although it is related to schema, it does not break anything. It is just weird to have a duplicated definition in standard ldif file and in 99user.ldif.
Thanks, Thierry! Setting to 1.3.3 backlog...
Per ticket triage, set milestone to FUTURE.
Metadata Update from @nhosoi: - Issue assigned to tbordaz - Issue set to the milestone: FUTURE
could be a duplicate of https://pagure.io/389-ds-base/issue/49215
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to None - Issue close_status updated to: None
Metadata Update from @mreynolds: - Issue tagged with: Schema
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/1081
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.