Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certain schema files are not replaced during upgrade #1192

Closed
389-ds-bot opened this issue Sep 12, 2020 · 8 comments
Closed

Certain schema files are not replaced during upgrade #1192

389-ds-bot opened this issue Sep 12, 2020 · 8 comments
Labels
closed: fixed Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47861


The schema for the dna plugin was changed with the fix for 47379. But the ldif was not added to the schema update script.

@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 12, 2020
@389-ds-bot 389-ds-bot added this to the 1.3.2.20 milestone Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from lkrispen (@elkris) at 2014-07-21 17:12:46

when fixing this we should also check if there are other schema changes which could be missed during upgrade

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-07-21 21:38:14

The following schema files need to be added to the upgrade script:

10dna-plugin.ldif
50ns-mail.ldif
60qmail.ldif
60radius.ldif
60samba3.ldif
60posix-winsync-plugin.ldif
60sabayon.ldif
60nis.ldif
60sendmail.ldif

@389-ds-bot
Copy link
Author

Comment from lkrispen (@elkris) at 2014-07-21 21:48:29

ack. just wondering if it wouldn't be better if the schema files would be listed in order 00xx .. 02xx 10xx ....

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-07-21 22:02:11

Replying to [comment:6 elkris]:

ack. just wondering if it wouldn't be better if the schema files would be listed in order 00xx .. 02xx 10xx ....

I was under the impression the numbering was only used for startup purposes, but just in case I redid the patch. New patch attached.

@389-ds-bot
Copy link
Author

@389-ds-bot
Copy link
Author

Comment from lkrispen (@elkris) at 2014-07-21 22:10:20

I think functionally the order is irrelevant, just easier to check if the file is already present in the list if you change a schema file

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-07-21 22:26:10

git merge ticket47861
Updating 65216ab..fe59338
Fast-forward
ldap/admin/src/scripts/60upgradeschemafiles.pl | 2 +-

65216ab..fe59338 master -> master
commit fe59338

da318fa..daffe97 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit daffe97

722117e..ba60488 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit ba604880431bc610c5dff92356b7c897d495f0a6

7dc69db..f1551fe 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit f1551fe

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-02-11 22:48:16

Metadata Update from @mreynolds389:

  • Issue assigned to mreynolds389
  • Issue set to the milestone: 1.3.2.20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant