389-ds-base

#49069 Schema learning mechanism should be able to merge diverging definitions of allowed attributes
Closed: wontfix by spichugi. Opened by tbordaz.

Closed: wontfix
Reopen Issue

When two replicated instances have a diverging definition of allowed attribute like

M1:
(objectclassA-oid NAME 'objectclassA' DESC 'xxx' SUP top MUST cn MAY ( attr1 $ attr2 ))
M2
(objectclassA-oid NAME 'objectclassA' DESC 'xxx' SUP top MUST cn MAY ( attr1 $ attr3 ))

The routine schema_oc_compare report that M1 > M2 because 'attr2' is not in M2 definition,
but it also reports M2 > M1 because of attr3 not being in M1.

As there is no subset and superset, the definition is not learned.

It should be possible to merge the definition with MAY (attr1 attr2 attr3)

Metadata Update from @tbordaz:
- Issue set to the milestone: 1.3.7 backlog

Metadata Update from @mreynolds:
- Issue close_status updated to: None
- Issue set to the milestone: 1.4 backlog (was: 1.3.7 backlog)

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- 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/2128

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

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)
Metadata
None

Schema

None
None
Normal
Community
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.