#47749 All standard schema definitions are present in 99user.ldif when the schema is updated in MMR
Opened 5 years ago by tbordaz. Modified 8 months ago

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:

  • Create a 2 masters
  • update the schema on one master adding a dummy 'objectclass'
  • add an entry on that master to trigger replication/schema update
  • Check that on the other master, 99user.ldif contains all schema objectclasses/attributes. (like 'top' objectclass)

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

2 years ago

Metadata Update from @tbordaz:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: None

8 months ago

Login to comment on this ticket.

Metadata