#285 database upgrade from v1 to v2 is broken
Closed: Fixed Opened by simo.

sysdb_upgrade_02 should upgrade automatically to the last version when creating new database files.


Fields changed

status: new => assigned

The problem here is because the upgrade_02 function doesn't complete immediately, it takes place later during the startup.

The correct approach is to run the upgrade_02 and then call upgrade_03 at the end of it, to ensure that the resulting files are on the correct version.

I'm not certain if it's completely necessary to call upgrade_03 at all, because upgrade_02 creates brand-new LDB files and may already update the case sensitivity (since it's removed from the default schema)

If this is the case, fixing this should be as easy as just saving the correct DB version to the new LDB file.

component: SSSD => SysDB
owner: sgallagh => sbose
status: assigned => new

Fixed by 307491c0bcb33c3b1f6004f81be5abe3f5ff5814

fixedin: => 1.0.0
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @simo:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.0

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1327

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