389-ds-base

#49419 schema - clean double oids
Closed: wontfix Opened by firstyear.

Closed: wontfix
Reopen Issue

Issue Description

It's been raised that we ship our schema with some attrs and objects with duplicated oids. We should correct this potentially by issuing our own oids to fix some types, and others we should assert rfc correctness of the schema,

That's not entirely true. We ship alternative schema files (with conflicting OIDs) in /usr/share/dirsrv/data, but they are not part of the standard schema - otherwise the server would not start if it detects there are duplicates ;-)

it's up to the admin to swap them in or out correctly.

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

Per triage meeting closing this as invalid

Metadata Update from @mreynolds:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

Hmmm okay, this was raised by someone that we do have duplicate oids in production and it does cause them issues ....

The server will faIl to start if there are duplicate oids. Try it ;-)

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/2478

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 (was: invalid)
Metadata
None
None
None
None
None
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.